-
Notifications
You must be signed in to change notification settings - Fork 87
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
Add relaxed names to nodeSelector property resolution. #464
Add relaxed names to nodeSelector property resolution. #464
Conversation
|
||
boolean hasGlobalNodeSelector = StringUtils.hasText(properties.getNodeSelector()); | ||
String nodeSelectorDeploymentProperty = deploymentProperties.getOrDefault(KubernetesDeployerProperties.KUBERNETES_DEPLOYMENT_NODE_SELECTOR, ""); | ||
for (String name : RelaxedNames.forCamelCase(KubernetesDeployerProperties.KUBERNETES_DEPLOYMENT_NODE_SELECTOR)) { |
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.
This solution will not work because KUBERNETES_DEPLOYMENT_NODE_SELECTOR
does not follow the KubernetesDeployment prefix format of spring.cloud.deployer.kubernetes
. It is currently spring.cloud.deployer.kubernetes.deployment
.
The addition of the RelaxedNames
does support when users use camel case instead of kabob case, but with the correct prefix.
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 PR!
But we need to update the prefix.
Closing this PR in light of the PR 466 issued by @corneil |
Whoops closed the wrong PR ! |
…DE_SELECTOR name.
Fixes #462