Giters

kubernetes-retired / multi-tenancy

A working place for multi-tenancy related proposals and prototypes.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

the tenant operator on ack deploy failed，requested access to the resource is denied

xiqiu618 opened this issue · comments

commented

fail to the tenant operator manifests image pull image [ImagePullBackOff]

➜  tmp kubectl get pods -n tenant-system controller-manager-0
NAME                   READY   STATUS             RESTARTS   AGE
controller-manager-0   0/1     ImagePullBackOff   0          12m

https://github.com/kubernetes-sigs/multi-tenancy/blob/8730dce091a78531a5fd21048262a01ecb633f4f/tenant/config/manager/all_in_one_ack.yaml#L212-L217

➜  .docker docker pull registry.cn-hangzhou.aliyuncs.com/virtualcluster/tenant
Using default tag: latest
Error response from daemon: pull access denied for registry.cn-hangzhou.aliyuncs.com/virtualcluster/tenant, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
commented

@xiqiu618 The tenant operator project will be deprecated. This is our very early attempt to support self-managed namespaces. We are moving to HNC for namespace as a service model and VirtualCluster for control plane as a service model. Let us know your requirements and we can point you to the proper project to start with.

commented

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

commented

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

commented

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:

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

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

/close

commented

@k8s-triage-robot: Closing this issue.

In response to this:

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:

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

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

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.