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

[BUG] kbcli install kubeblocks set image.registry not effect #444

Open
JashBook opened this issue Sep 23, 2024 · 2 comments
Open

[BUG] kbcli install kubeblocks set image.registry not effect #444

JashBook opened this issue Sep 23, 2024 · 2 comments
Assignees
Labels
bug Something isn't working Stale

Comments

@JashBook
Copy link
Collaborator

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

  1. install kubeblocks
kbcli kubeblocks install --create-namespace --version 0.9.1-beta.27 --set image.registry=apecloud-registry.cn-zhangjiakou.cr.aliyuncs.com --set dataProtection.image.registry=apecloud-registry.cn-zhangjiakou.cr.aliyuncs.com --set addonChartsImage.registry=apecloud-registry.cn-zhangjiakou.cr.aliyuncs.com --set admissionWebhooks.enabled=true --set admissionWebhooks.ignoreReplicasCheck=true --set dataProtection.image.datasafed.tag=0.2.0  --namespace kb-system

Kubernetes version 1.31.0
kbcli version 0.9.1-beta.10
Collecting data from cluster                       OK
Kubernetes cluster preflight                       OK
  Warn
  - This application requires at least 3 nodes
Create CRDs                                        OK
Add and update repo kubeblocks                     OK
Install KubeBlocks 0.9.1-beta.27                   OK
Wait for addons to be enabled
  apecloud-mysql                                   OK
  etcd                                             OK
  kafka                                            OK
  mongodb                                          OK
  mysql                                            OK
  postgresql                                       OK
  pulsar                                           OK
  redis                                            OK
  snapshot-controller                              OK

KubeBlocks 0.9.1-beta.27 installed to namespace kb-system SUCCESSFULLY!

-> Basic commands for cluster:
    kbcli cluster create -h     # help information about creating a database cluster
    kbcli cluster list          # list all database clusters
    kbcli cluster describe <cluster name>  # get cluster information

-> Uninstall KubeBlocks:
    kbcli kubeblocks uninstall
  1. See error
helm get values -n kb-system kubeblocks
USER-SUPPLIED VALUES:
addonChartsImage:
  registry: apecloud-registry.cn-zhangjiakou.cr.aliyuncs.com
admissionWebhooks:
  enabled: true
  ignoreReplicasCheck: true
dataProtection:
  image:
    datasafed:
      tag: 0.2.0
    registry: apecloud-registry.cn-zhangjiakou.cr.aliyuncs.com
image:
  registry: docker.io
tolerations:
- effect: NoSchedule
  key: kb-controller
  operator: Equal
  value: "true"

describe kubeblocks deploy

kubectl describe deployments.apps -n kb-system kubeblocks
Name:                   kubeblocks
Namespace:              kb-system
CreationTimestamp:      Mon, 23 Sep 2024 11:48:36 +0800
Labels:                 app.kubernetes.io/component=apps
                        app.kubernetes.io/instance=kubeblocks
                        app.kubernetes.io/managed-by=Helm
                        app.kubernetes.io/name=kubeblocks
                        app.kubernetes.io/version=0.9.1-beta.27
                        helm.sh/chart=kubeblocks-0.9.1-beta.27
Annotations:            deployment.kubernetes.io/revision: 1
                        meta.helm.sh/release-name: kubeblocks
                        meta.helm.sh/release-namespace: kb-system
Selector:               app.kubernetes.io/component=apps,app.kubernetes.io/instance=kubeblocks,app.kubernetes.io/name=kubeblocks
Replicas:               1 desired | 1 updated | 1 total | 1 available | 0 unavailable
StrategyType:           RollingUpdate
MinReadySeconds:        0
RollingUpdateStrategy:  40% max unavailable, 1 max surge
Pod Template:
  Labels:           app.kubernetes.io/component=apps
                    app.kubernetes.io/instance=kubeblocks
                    app.kubernetes.io/name=kubeblocks
  Service Account:  kubeblocks
  Init Containers:
   tools:
    Image:      docker.io/apecloud/kubeblocks-tools:0.9.1-beta.27
    Port:       <none>
    Host Port:  <none>
    Command:
      /bin/true
    Environment:  <none>
    Mounts:       <none>
   datascript:
    Image:      docker.io/apecloud/kubeblocks-datascript:0.9.1-beta.27
    Port:       <none>
    Host Port:  <none>
    Command:
      /bin/true
    Environment:  <none>
    Mounts:       <none>
  Containers:
   manager:
    Image:       docker.io/apecloud/kubeblocks:0.9.1-beta.27
    Ports:       9443/TCP, 8081/TCP, 8080/TCP
    Host Ports:  0/TCP, 0/TCP, 0/TCP
    Args:
      --health-probe-bind-address=:8081
      --metrics-bind-address=:8080
      --leader-elect
      --zap-devel=false
      --zap-time-encoding=iso8601
      --zap-encoder=console
      --extensions=true
      --apps=true
      --workloads=true
      --experimental=false
      --user-agent=kubeblocks
    Liveness:   http-get http://:health/healthz delay=15s timeout=1s period=20s #success=1 #failure=3
    Readiness:  http-get http://:health/readyz delay=5s timeout=1s period=10s #success=1 #failure=3
    Environment:
      CM_NAMESPACE:                           kb-system
      CM_AFFINITY:                            {"nodeAffinity":{"preferredDuringSchedulingIgnoredDuringExecution":[{"preference":{"matchExpressions":[{"key":"kb-controller","operator":"In","values":["true"]}]},"weight":100}]}}
      CM_TOLERATIONS:                         [{"effect":"NoSchedule","key":"kb-controller","operator":"Equal","value":"true"}]
      KUBEBLOCKS_IMAGE_PULL_POLICY:           IfNotPresent
      KUBEBLOCKS_IMAGE_PULL_SECRETS:          []
      KUBEBLOCKS_TOOLS_IMAGE:                 docker.io/apecloud/kubeblocks-tools:0.9.1-beta.27
      KUBEBLOCKS_DATASCRIPT_CLIENTS_IMAGE:    docker.io/apecloud/kubeblocks-datascript:0.9.1-beta.27
      KUBEBLOCKS_SERVICEACCOUNT_NAME:         kubeblocks
      VOLUMESNAPSHOT_API_BETA:                false
      ENABLE_WEBHOOKS:                        true
      ENABLE_RBAC_MANAGER:                    true
      ADDON_JOB_TTL:                          
      ADDON_JOB_IMAGE_PULL_POLICY:            IfNotPresent
      KUBEBLOCKS_ADDON_SA_NAME:               kubeblocks-addon-installer
      KUBEBLOCKS_ADDON_HELM_INSTALL_OPTIONS:  --atomic --cleanup-on-fail --wait --insecure-skip-tls-verify
      DP_ENCRYPTION_KEY:                      <set to the key 'dataProtectionEncryptionKey' in secret 'kubeblocks-secret'>  Optional: false
      KUBE_PROVIDER:                          
      HOST_PORT_INCLUDE_RANGES:               1025-65536
      HOST_PORT_EXCLUDE_RANGES:               6443,10250,10257,10259,2379-2380,30000-32767
      HOST_PORT_CM_NAME:                      kubeblocks-host-ports
      COMPONENT_REPLICAS_ANNOTATION:          true
      IN_PLACE_POD_VERTICAL_SCALING:          false
      NO_RSM_ENV:                             false
    Mounts:
      /etc/kubeblocks from manager-config (rw)
      /tmp/k8s-webhook-server/serving-certs from cert (ro)
  Volumes:
   manager-config:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      kubeblocks-manager-config
    Optional:  false
   cert:
    Type:          Secret (a volume populated by a Secret)
    SecretName:    kubeblocks.kb-system.svc.tls-pair
    Optional:      false
  Node-Selectors:  <none>
  Tolerations:     kb-controller=true:NoSchedule
Conditions:
  Type           Status  Reason
  ----           ------  ------
  Available      True    MinimumReplicasAvailable
  Progressing    True    NewReplicaSetAvailable
OldReplicaSets:  <none>
NewReplicaSet:   kubeblocks-7fb544c48d (1/1 replicas created)
Events:
  Type    Reason             Age    From                   Message
  ----    ------             ----   ----                   -------
  Normal  ScalingReplicaSet  5m11s  deployment-controller  Scaled up replica set kubeblocks-7fb544c48d to 1

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: [e.g. iOS]
  • Browser [e.g. chrome, safari]
  • Version [e.g. 22]

Additional context
Add any other context about the problem here.

@JashBook JashBook added the bug Something isn't working label Sep 23, 2024
@JashBook
Copy link
Collaborator Author

replace by .kbcli/config.yaml file

cat .kbcli/config.yaml
auth_url: https://apecloud.authing.cn/oidc
clearresourcepollinginterval: 1ms
clearresourcetimeout: 10s
client_id: 64e42ca02df49bffa50719a9
cluster_default_cpu: 1000m
cluster_default_memory: 1Gi
cluster_default_replicas: 1
cluster_default_storage_size: 20Gi
consistentlyduration: 3s
consistentlypollinginterval: 1ms
eventuallypollinginterval: 1ms
eventuallytimeout: 10s
helm_repo_url: ""
image_registry: docker.io
kb_max_lag: 10
kb_ttl: 15
kill_container_signal: SIGKILL
kubernetes_cluster_domain: cluster.local
openapi_server: https://cloudapi.apecloud.cn

Copy link

This issue has been marked as stale because it has been open for 30 days with no activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Stale
Projects
None yet
Development

No branches or pull requests

3 participants