kubebuilder icon indicating copy to clipboard operation
kubebuilder copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes-sigs

Whether multiple domains can be configured

Open wenchajun opened this issue 4 years ago • 16 comments
trafficstars

What do you want to happen?

Hello, everyone. I have a question about whether KubeBuilder can configure multiple domains. I looked it up, but it was rarely mentioned. So I want to ask here if I can configure multiple domains. If yes, how to configure it. thanks

Extra Labels

/kind documentation

wenchajun avatar Oct 22 '21 07:10 wenchajun

I want to put multiple domains under one REPO. Is this possible? Is there documentation.

wenchajun avatar Oct 22 '21 08:10 wenchajun

When you init the project you define the domain. Then, you will create GVK for this domain by creating APIs for that. More info: https://book.kubebuilder.io/cronjob-tutorial/gvks.html and https://book.kubebuilder.io/cronjob-tutorial/new-api.html.

You can define multi groups for the same domain. See: https://book.kubebuilder.io/migration/multi-group.html

Also, you can use scaffold APIs to reconcile Kinds that were defined in another project as well.

However, could you please let us know why a project should have more than one domain?

camilamacedo86 avatar Oct 27 '21 09:10 camilamacedo86

Thanks for your reply. Because I want to have two domain names under one repository. The repository was developed in collaboration with two organizations. Any suggestions would be appreciated!

wenchajun avatar Oct 27 '21 09:10 wenchajun

@wenchajun Currently, we don't support that feature, but we are evaluating the use cases for being able to support more than one domain in the same project. To answer your question, currently there is no way to support configuration of multiple domains.

Are you interested in collaborating on this?

rashmigottipati avatar Dec 02 '21 17:12 rashmigottipati

/assign @pjbgf

rashmigottipati avatar Dec 02 '21 17:12 rashmigottipati

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Mar 16 '22 17:03 k8s-triage-robot

/remove-lifecycle stale

pjbgf avatar Mar 21 '22 07:03 pjbgf

/remove-lifecycle stale

camilamacedo86 avatar Mar 21 '22 09:03 camilamacedo86

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Jun 19 '22 10:06 k8s-triage-robot

/remove-lifecycle stale

camilamacedo86 avatar Jun 19 '22 11:06 camilamacedo86

/remove-lifecycle stale

camilamacedo86 avatar Jul 11 '22 18:07 camilamacedo86

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Oct 09 '22 19:10 k8s-triage-robot

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot avatar Nov 08 '22 20:11 k8s-triage-robot

/remove-lifecycle rotten

camilamacedo86 avatar Sep 11 '23 08:09 camilamacedo86