-
Notifications
You must be signed in to change notification settings - Fork 979
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
🐛 Fix Pod spec toleration when the spec is a template #2380
Open
arybolovlev
wants to merge
6
commits into
main
Choose a base branch
from
fix-tolerations-in-templates
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
arybolovlev
changed the title
Add a new argument to function
🐛 Fix Pod spec toleration when the spec is a template
Jan 2, 2024
flattenPodSpec
Hello @arybolovlev Any expected date for when this will be merged? Best regards |
sheneska
reviewed
May 2, 2024
@@ -38,7 +38,7 @@ func flattenOS(in v1.PodOS) []interface{} { | |||
return []interface{}{att} | |||
} | |||
|
|||
func flattenPodSpec(in v1.PodSpec) ([]interface{}, error) { | |||
func flattenPodSpec(in v1.PodSpec, isTeamplate bool) ([]interface{}, error) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the changes @arybolovlev, should this be isTeamplate bool
or isTemplate bool
?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR updates the logic of resources that use the Pod specification template and now the provider will keep all tolerations(
spec.toleration
) returned by Kubernetes. The same is applicable for the data sourceskubernetes_pod_v1
andkubernetes_pod
. The behavior of resourceskubernetes_pod_v1
andkubernetes_pod
remains unchanged, i.e. the provider will keep removing tolerations with well-known taints since they might be attached to the object by Kubernetes controller and could lead to a perpetual diff.Affected resources and data sources:
resource/kubernetes_replication_controller
resource/kubernetes_replication_controller_v1
resource/kubernetes_stateful_set
resource/kubernetes_stateful_set_v1
resource/kubernetes_deployment
resource/kubernetes_deployment_v1
resource/kubernetes_daemonset
resource/kubernetes_daemon_set_v1
resource/kubernetes_cron_job
resource/kubernetes_cron_job_v1
resource/kubernetes_job
resource/kubernetes_job_v1
data_source/kubernetes_pod
data_source/kubernetes_pod_v1
Acceptance tests
Release Note
Release note for CHANGELOG:
References
Fix: #2376
Community Note