Encountering errors when installing VKS Cluster Management (VKSm) auto-attach service from vSphere Cloud Foundation Automation | Provider Management under Services -> Overview.
When viewing the status of the VKS Cluster Management auto-attach service, an error message similar to the following is returned, specifically 405 Method Not Allowed:
failed to authorize: failed to fetch anonymous token: unexpected status from GET request to https://mgmt-image-proxy.kube-system.svc.cluster.local/oauth/provider/token?scope=repository%3Abroadcom%2Fauto-attach-service%2F0.1.0%2Fauto-attach-service%3Apull: 405 Method Not Allowed" image="mgmt-image-proxy.kube-system.svc.cluster.local/broadcom/auto-attach-service/0.1.0/auto-attach-service@sha256:<sha>"
vCenter 9.X
vSphere Supervisor 9.X
vSphere Cloud Foundation Automation 9.X
A pre-requisite for installing VKS Cluster Management (VKSm) in the environment was missed.
Supervisor management proxy supervisor service must be installed and healthy in the environment in order to install VKS Cluster Management.
Supervisor Management Proxy supervisor service is a requirement for installing VKS Cluster Management in the environment.
Follow the documentation to install Supervisor Management Proxy service under Supervisor Management in the vSphere web client:
Starting in VCF 9.1, supervisor services for VCF 9.1 that integrate with VCF Automation require that Regional Harbor or its equivalent is set up in the environment. Installing Regional Harbor will set up a Supervisor Cluster Container Registry for depot.kube-system.svc.
"You need a proxy to enable the communication between the auto-attach service that runs in the Supervisor and the VKS cluster management feature in VCF Automation"
Enabling VKS Cluster Management