Skip to content

Conversation

@zentron
Copy link
Contributor

@zentron zentron commented Jan 9, 2026

When running the agent locally, ill often have any number of different kubectl contexts and namespaces that I want the agent to connect with.

This PR adds a little more configuration support based on env variables

@zentron zentron requested a review from a team as a code owner January 9, 2026 04:26
@zentron zentron force-pushed the robe/local-k8scontext branch from 59fa0e7 to e3b8865 Compare January 9, 2026 04:26
};

var namespaceVar = Environment.GetEnvironmentVariable("OCTOPUS__K8STENTACLE__NAMESPACE");
var namespaceVar = Environment.GetEnvironmentVariable(KubernetesConfig.NamespaceVariableName);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think only the namespace configuration is duplicated across the Telepresence and normal configurations. When/if we have more duplication then it's worth extracting out the common stuff

Copy link
Contributor

@flin-8 flin-8 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants