Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Consider using external addons #253

Closed
wolfedale opened this issue Jan 29, 2019 · 10 comments
Closed

Consider using external addons #253

wolfedale opened this issue Jan 29, 2019 · 10 comments
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence.

Comments

@wolfedale
Copy link

I noticed that k8s cluster created by kind don't have any additional addons, for example there is no ingress, nginx or default backend. Somehow I need to test my ingress (nginx/traefik) and I'm wondering if it make sense to add this kind of option to the kind. Of course we can leave it as it is, but then I would need to execute my ingress configuration files each time I will create new cluster.

Does it make sense?

@neolit123
Copy link
Member

by allowing commands on nodes we can achieve that.
i have a proposal for that in this ticket:
#252

@BenTheElder
Copy link
Member

Today in SIG-cluster-lifecycle there is discussion of a potential shared addon management solution kubernetes/enhancements#746 (currently ongoing)

I think in the meantime we can try to document and make it easier to install these things without necessarily committing to shipping one built-in yet.

I'm thinking about ways we can make this faster and easier without bundling a particular version / implementation just to avoid the project having scope explosion.

@BenTheElder BenTheElder added priority/backlog Higher priority than priority/awaiting-more-evidence. kind/feature Categorizes issue or PR as related to a new feature. labels Feb 6, 2019
@BenTheElder BenTheElder added this to the 2019 goals milestone Feb 6, 2019
@BenTheElder
Copy link
Member

Still keeping a close eye on the SIG Cluster Lifecycle addons work. there are regular meetings and a slack channel for this now, continuing to keep tabs on how that effort is going. I'd like to not duplicate effort there if possible.

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 3, 2019
@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Aug 2, 2019
@BenTheElder BenTheElder added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Aug 2, 2019
@kubernetes-sigs kubernetes-sigs deleted a comment from fejta-bot Aug 2, 2019
@kubernetes-sigs kubernetes-sigs deleted a comment from fejta-bot Aug 2, 2019
@BenTheElder
Copy link
Member

No major updates on this just yet, still monitoring the cluster lifecycle work.
Freezing the issue for now as we're watching how this goes in the broader project while tackling other work for now.

@dholbach
Copy link
Member

With kubernetes/kubernetes#85224 getting closer to the finish line, the work could potentially be exposed and used in kind too?

@BenTheElder
Copy link
Member

Likely yes, also note that all kubeadm config options are available to power users via config patches, so without even properly exposing it this will be possible to experiment with 😅

@cmoulliard
Copy link

So, the feature requested by this ticket will be in fact managed by some kubernetes cluster addons = operators (https://github.com/kubernetes-sigs/cluster-addons) - correct ?

@BenTheElder
Copy link
Member

Undecided. I'm not sure where the project is at currently, this is on our backlog along with many things.

@BenTheElder
Copy link
Member

BTW Ingress is a trickier case (due to docker networking), documented at https://kind.sigs.k8s.io/docs/user/ingress/

@BenTheElder BenTheElder removed this from the 2020 goals milestone Jan 25, 2021
@BenTheElder
Copy link
Member

Ingress: https://kind.sigs.k8s.io/docs/user/ingress/ (pick your own, need to align some cluster configuration for networking unfortunately due to docker)
Loadbalancer: https://kind.sigs.k8s.io/docs/user/loadbalancer/ (note: perhaps not very useful on mac and windows)

I think iff https://github.com/kubernetes-sigs/cluster-addons or similar gets traction they can be used against kind without any work here. Currently cluster-addons seems rather inactive. Last commit ~6 months ago.

@BenTheElder BenTheElder self-assigned this Jun 24, 2021
yankay pushed a commit to yankay/kind that referenced this issue Mar 17, 2022
Code changes to handle service updates
stg-0 pushed a commit to stg-0/kind that referenced this issue Sep 6, 2023
…netes-sigs#253)

* chore: Update several components version

* changelog

* new version clusterawsadm

---------

Co-authored-by: Francisco Augusto <faugusto@stratio.com>
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Development

No branches or pull requests

6 participants