Skip to content

Failure to access public chart: 401 Unauthorized when applying wordpress-service-composition.yaml using kubeplus-saas-provider.json #1442

@prathameshk03

Description

@prathameshk03

I am trying to deploy the sample wordpress-service-composition.yaml provided in the KubePlus repository. However, I am encountering a 401 Unauthorized error when applying the YAML file using the kubeplus-saas-provider.json kubeconfig.

Environment:

  • OS: Ubuntu 24.04 (WSL2)
  • Minikube version: v1.36.0
  • Kubernetes version: v1.33.1 (via Minikube)
  • Kubectl client version: v1.33.2
  • KubePlus deployment status: Running (1/1 pod available)
  • Helm install: Successful

Steps to Reproduce:

  1. Starting MiniKube with Docker driver
minikube start --driver=docker
kubectl create ns kubeplus
  1. Deploy KubePlus using Helm (worked successfully):
cd kubeplus/deploy/kubeplus-chart
helm install kubeplus ./ -n kubeplus
  1. Verify pods (KubePlus is running):
kubectl get pods -n kubeplus
  1. Try applying the public chart:

kubectl create -f https://raw.githubusercontent.com/cloud-ark/kubeplus/master/examples/multitenancy/application-hosting/wordpress/wordpress-service-composition.yaml \
  --kubeconfig=kubeplus-saas-provider.json \
  -n kubeplus \
  -v6 --validate=false

Instead of WordPress Service Composition being created successfully, I am getting the following error.
Error returned:

[{
  "kind": "Status",
  "apiVersion": "v1",
  "metadata": {},
  "status": "Failure",
  "message": "error when creating \"https://raw.githubusercontent.com/cloud-ark/kubeplus/master/examples/multitenancy/application-hosting/wordpress/wordpress-service-composition.yaml\": Unauthorized",
  "reason": "Unauthorized",
  "code": 401
}]
error: You must be logged in to the server (error when creating ".../wordpress-service-composition.yaml": Unauthorized)

Additional context:
Output of kubectl describe deployment kubeplus-deployment -n kubeplus shows the pod has 5 containers (kubeconfiggenerator, crd-hook, platform-operator, consumerui, helmer) and is Running with no recent errors.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions