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

POC and documentation on how to setup MCM on non-gardener k8s cluster #770

Open
1 task
unmarshall opened this issue Jan 24, 2023 · 1 comment
Open
1 task
Labels
area/control-plane Control plane related area/dev-productivity Developer productivity related (how to improve development) area/documentation Documentation related area/usability Usability related kind/enhancement Enhancement, improvement, extension lifecycle/stale Nobody worked on this for 6 months (will further age) needs/planning Needs (more) planning with other MCM maintainers priority/3 Priority (lower number equals higher priority)

Comments

@unmarshall
Copy link
Contributor

unmarshall commented Jan 24, 2023

How to categorize this issue?

/area control-plane
/area dev-productivity
/area usability
/area documentation
/kind enhancement
/priority 3

What would you like to be added:
#768 raises an important gap that we have currently. We should work towards improving the usability of MCM outside gardener context and also provide a local KIND based setup using which developers/adopters outside gardener can play around with MCM.

We should aim to achieve the following:

  • Choose any given infrastructure provider and setup MCM on the managed k8s that is provided out of the box from the provider or any k8s installation that is separately been setup on any infrastructure provider. This should also include the following (the list is not complete and needs to be enhanced as and when we find the gaps)
  • Update the documentation to provide how to build MCM docker image (out-of-tree) for a specific provider using provider-extensions.
  • Provide documentation on how to setup a KIND cluster with local provider and MCM.
  • Proposal to improve documentation across providers

What should not be covered?

  • Setup of k8s

Why is this needed:
To ease MCM adoption in the community

@unmarshall unmarshall added the kind/enhancement Enhancement, improvement, extension label Jan 24, 2023
@gardener-robot gardener-robot added area/control-plane Control plane related area/dev-productivity Developer productivity related (how to improve development) area/documentation Documentation related area/usability Usability related priority/3 Priority (lower number equals higher priority) labels Jan 24, 2023
@unmarshall unmarshall changed the title POC and Documentation on hw to POC and Documentation on how to setup MCM on non-gardener k8s cluster Jan 24, 2023
@unmarshall unmarshall changed the title POC and Documentation on how to setup MCM on non-gardener k8s cluster POC and documentation on how to setup MCM on non-gardener k8s cluster Jan 24, 2023
@elankath elankath self-assigned this Jan 25, 2023
@elankath
Copy link
Contributor

will commence this after grooming.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/control-plane Control plane related area/dev-productivity Developer productivity related (how to improve development) area/documentation Documentation related area/usability Usability related kind/enhancement Enhancement, improvement, extension lifecycle/stale Nobody worked on this for 6 months (will further age) needs/planning Needs (more) planning with other MCM maintainers priority/3 Priority (lower number equals higher priority)
Projects
None yet
Development

No branches or pull requests

5 participants