Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add a "strict mode" that requires "kubeconfig" and "context" #2423

Closed
lblackstone opened this issue May 23, 2023 · 0 comments 路 Fixed by #2425
Closed

Add a "strict mode" that requires "kubeconfig" and "context" #2423

lblackstone opened this issue May 23, 2023 · 0 comments 路 Fixed by #2425
Assignees
@lblackstone
Labels
impact/reliability Something that feels unreliable or flaky impact/security impact/usability Something that impacts users' ability to use the product easily and intuitively kind/enhancement Improvements or new features resolution/fixed This issue was fixed
Milestone
0.89

Comments

@lblackstone
Copy link
Member

Hello!

  • Vote on this issue by adding a 馃憤 reaction
  • If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

Following on from discussion in #2357 and #1853, we should add a "strict mode" that adds extra checking to the provider configuration. This mode would include the following:

  1. Disables default Kubernetes provider to avoid resources being deployed to the ambient cluster config
  2. Requires the kubeconfig parameter to be specified for any Kubernetes Provider in the stack
  3. Requires the context parameter to be specified for any Kubernetes Provider in the stack

This mode could be enabled with a project/stack configuration similar to the existing pulumi:disable-default-providers option.

Affected area/feature
@lblackstone lblackstone added impact/usability Something that impacts users' ability to use the product easily and intuitively impact/security impact/reliability Something that feels unreliable or flaky kind/enhancement Improvements or new features labels May 23, 2023
This was referenced May 23, 2023
Closed
Closed
Closed
Merged
@lblackstone lblackstone self-assigned this May 24, 2023
@lblackstone lblackstone added this to the 0.89 milestone May 24, 2023
@pulumi-bot pulumi-bot added the resolution/fixed This issue was fixed label May 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lblackstone lblackstone

Labels
impact/reliability Something that feels unreliable or flaky impact/security impact/usability Something that impacts users' ability to use the product easily and intuitively kind/enhancement Improvements or new features resolution/fixed This issue was fixed
Projects
None yet
Milestone
0.89
Development

Successfully merging a pull request may close this issue.

Add a "strict mode" configuration option pulumi/pulumi-kubernetes
2 participants
@lblackstone @pulumi-bot