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.

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

chore(kuma-cp) support other service name in DP injector #1491

Merged
merged 4 commits into from
Jan 29, 2021

Conversation

jakubdyszkiewicz
Copy link
Contributor

Summary

Full changelog

  • Introduced kuma_runtime_kubernetes_control_plane_service_name so Kuma the service name change can be applied and injector will inject Kuma DP with proper URL
  • Kuma CNI was used hardcoded kuma-cni service account name where as the service account was created with this pattern serviceAccountName: {{ include "kuma.name" . }}-cni
  • Expanded golden file test infrastructure. Introduced proper matcher.
  • Extracted expect many YAML files in install to 1 function and introduced update golden to all install files.
  • We are now excluding all files that contains templates/pre-", templates/post-, not only prefix. This way when kuma is a sub chart, it will work.
  • Exposed some e2e test constants regarding CNI.

Documentation

  • No docs, internal changes only.

Signed-off-by: Jakub Dyszkiewicz <jakub.dyszkiewicz@gmail.com>
@jakubdyszkiewicz jakubdyszkiewicz requested a review from a team as a code owner January 28, 2021 18:17
Copy link
Contributor

@nickolaev nickolaev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks perfectly fine to me! LGTM

Signed-off-by: Jakub Dyszkiewicz <jakub.dyszkiewicz@gmail.com>
Signed-off-by: Jakub Dyszkiewicz <jakub.dyszkiewicz@gmail.com>
@@ -687,4 +687,4 @@ spec:
secret:
secretName: loki
- name: storage
emptyDir: {}
emptyDir: {}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does it mean a new update mode for golden files isn't adding an empty line at the end?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe. It's just overriding file with the output content. If content has no empty line at the end, there won't be empty line in the golden file. Is that a problem?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, no problem, GitHub so much highlights the fact there is no empty line at the end, so I asked :)

}

func MatchGoldenJSON(goldenFilePath string) types.GomegaMatcher {
return MatchGolden(gomega.MatchYAML, goldenFilePath)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it should be MatchJSON

Signed-off-by: Jakub Dyszkiewicz <jakub.dyszkiewicz@gmail.com>
@jakubdyszkiewicz jakubdyszkiewicz merged commit 4d2d01c into master Jan 29, 2021
@jakubdyszkiewicz jakubdyszkiewicz deleted the chore/helm-test-params branch January 29, 2021 14:53
mergify bot pushed a commit that referenced this pull request Jan 29, 2021
Signed-off-by: Jakub Dyszkiewicz <jakub.dyszkiewicz@gmail.com>
(cherry picked from commit 4d2d01c)

# Conflicts:
#	app/kumactl/pkg/install/k8s/control-plane/helmtemplates_vfsdata.go
#	mk/e2e.new.mk
nickolaev pushed a commit that referenced this pull request Feb 4, 2021
…1494)

* chore(kuma-cp) support other service name in DP injector (#1491)

Signed-off-by: Jakub Dyszkiewicz <jakub.dyszkiewicz@gmail.com>
(cherry picked from commit 4d2d01c)

# Conflicts:
#	app/kumactl/pkg/install/k8s/control-plane/helmtemplates_vfsdata.go
#	mk/e2e.new.mk

* fix(*) conflicts

Signed-off-by: Nikolay Nikolaev <nikolay.nikolaev@konghq.com>

Co-authored-by: Jakub Dyszkiewicz <jakub.dyszkiewicz@gmail.com>
Co-authored-by: Nikolay Nikolaev <nikolay.nikolaev@konghq.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants