Cherry-pick #20627 to 7.x: Ensure kind cluster has RFC1123 compliant name#20893
Merged
blakerouse merged 1 commit intoelastic:7.xfrom Sep 22, 2020
Merged
Cherry-pick #20627 to 7.x: Ensure kind cluster has RFC1123 compliant name#20893blakerouse merged 1 commit intoelastic:7.xfrom
blakerouse merged 1 commit intoelastic:7.xfrom
Conversation
When creating a kind cluster, we must use a cluster name that is a valid Kubernetes resource name, and by extension, a valid DNS name. If not, kind cluster provisioning can fail when kind tries to create resources with invalid names. For example, if trying to create a cluster called "a_b" (underscores are not permitted), control-plane provisioning will fail with: host 'a_b-control-plane' must be [...] a valid RFC-1123 DNS subdomain (cherry picked from commit 345e045)
Contributor
|
Pinging @elastic/integrations-platforms (Team:Platforms) |
Contributor
💔 Tests Failed
Expand to view the summary
Build stats
Test stats 🧪
Test errorsExpand to view the tests failures
Steps errorsExpand to view the steps failures
Log outputExpand to view the last 100 lines of log output
|
Contributor
Author
|
CI failures are un-related to this backport. |
exekias
approved these changes
Sep 22, 2020
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Cherry-pick of PR #20627 to 7.x branch. Original message:
What does this PR do?
This patch:
-where it previously produced_kubernetesPodNametokubernetesClusterName, reflecting its purposeWhy is it important?
When creating a kind cluster, we must use a cluster name that is a valid Kubernetes resource name, and by extension, a valid DNS name. If not, kind cluster provisioning can fail when kind tries to create resources with invalid names.
For example, if trying to create a cluster called "a_b" (underscores are not permitted), control-plane provisioning will fail with:
With this patch, the
kubernetesMetricbeat module integration tests are able to run to completion on my system. Without it,kindfails in this manner:Checklist
I have made corresponding changes to the documentationI have made corresponding change to the default configuration filesI have added tests that prove my fix is effective or that my feature worksI have added an entry inCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.How to test this PR locally
Run the integ tests for the
kubernetesMetricbeat module with Mage in verbose mode.kindwill be seen to run correctly. Without the patchkindwill fail to provision the control-plane.With Mage not in verbose mode, the
kubernetesinteg test is not run, and no output is seen (because it dies at setup time).