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

Cleanup Kustomize #9

Open
palladius opened this issue Jul 11, 2022 · 1 comment
Open

Cleanup Kustomize #9

palladius opened this issue Jul 11, 2022 · 1 comment
Assignees
Labels
help wanted Extra attention is needed question Further information is requested

Comments

@palladius
Copy link
Owner

palladius commented Jul 11, 2022

3 problems with kustomize:

  • code is scattered across 2 dirs, should be in one only: see below
  • code was just a test for me to learn, and 2 weeks after is destined to become the number one repo on github :) I need some cleanup and make sure it all works.
  • Does it make sense to use kustomize at all? I mean, the ONLY use which is REALLY important is: canary 9 pods, prod 1 pod. And a common selector for canary and prod. Coudl I just create 4 copies of k8s manifests to increase readability?

I'd love a kustomize expert to help me on this.

scattered code (1)

ricc@ricc:~/git/clouddeploy-platinum-path$ 🐼 find . -name components
./components
./apps/components
@palladius
Copy link
Owner Author

Alex, I can of coruse merge the two components folder, I just you to tell me:

  1. Q1. Where should I put the components folder: which to keep and which to kill?
  2. Q3. Does it make sense to have kustomize at all for my use case? Think of the N users who'll read the blog. Do they need that extra complexity?

the 'betterification' fo code can be done at later stage :)

@palladius palladius added help wanted Extra attention is needed question Further information is requested labels Jul 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants