-
Notifications
You must be signed in to change notification settings - Fork 975
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.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kubernetes_deployment does not support namespace_selector for pod_anti_affinity #1826
Comments
@alexsomesan, I can see other resources already have support for |
Marking this issue as stale due to inactivity. If this issue receives no comments in the next 30 days it will automatically be closed. If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. This helps our maintainers find and focus on the active issues. Maintainers may also remove the stale label at their discretion. Thank you! |
I can confirm that also in The block |
Hello, is there any plan to implement this ? |
just noticed this PR: #2020 |
@aayushsss1 this is a good issue to pick up. involves adding a new field which is not blocked by a k8s version block. You're open to work on it since the previous PR was closed a few months back. |
@BBBmau sure I'll take a look into this! |
@BBBmau It looks like namespace_selector is already supported for pod affinity and pod anti-affinity. Could you please let me know what additional work is required on this? Thanks! terraform-provider-kubernetes/kubernetes/schema_affinity_spec.go Lines 169 to 176 in af55e47
|
You're right! Just looked and we recently merged this that add support not too long ago #2577 It addressed this issue which is a duplicate of this one. So we can mark this as completed. Thanks for spotting it @aayushsss1 ! |
Description
It looks like neither
kubernetes_deployment
norkubernetes_deployment_v1
support the namespace_selector field forpod_anti_affinity
(and possibly forpod_affinity
). This is unfortunate, because it is the only way to specify a match in "all namespaces" (by passing an empty selector).Potential Terraform Configuration
References
n / a
Community Note
The text was updated successfully, but these errors were encountered: