You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 4, 2026. It is now read-only.
Initial design should be a wrapper around kubectl. This will result in kubectl being a dependency on this module. However, the design should provide an abstraction so that in the future we can introduce the dotnet sdk for k8s or a powershell sdk if one is created.
Stories
As a user, I would like to instantiate a new Kubernetes client so that I can fetch data.
The ability to use a .kubeconfig file for authorization
The ability to use a KUBECONFIG environment variable for authorization
As a user, I would like to list pods in a namespace.
As a user, I would like to list namespaces.
As a user, I would like to list services.
As a user, I would like to list ingresses.
As a user, I would like to set up a port-forward tunnel so that the test is able to get to internal Api calls.
As a user, I would like to verify that a Kubernetes secret exist. Note, this should NOT retrieve the secret value and only ensure that a secret is present in k8s.
As a user I would like to verify that PVC and PV exist.
Spike initial Module Surface with stub methods for implementation.
Design K8sClient abstract interface that will abstract underlying calls.
Summary
Initial design should be a wrapper around kubectl. This will result in kubectl being a dependency on this module. However, the design should provide an abstraction so that in the future we can introduce the dotnet sdk for k8s or a powershell sdk if one is created.
Stories
AC