container-service-extension icon indicating copy to clipboard operation
container-service-extension copied to clipboard

Container Service for VMware vCloud Director

Results 91 container-service-extension issues
Sort by recently updated
recently updated
newest added

- Need step by step procedure for upgrade CSE 2.0.0 to CSE 2.5.1 - List of actions which can/can’t be performed on existing cluster after upgrade from CSE 2.0.0 to...

question

Hello, I don't know if it's an issue, but our security team find a strange behavior where the api accept the cluster creation request if you are setting org_name and...

question

Hi everyone, I'm not sure if this is an issue or just a question, anyway I'm gonna expose my case here to see if someone may shed some light on...

question

Following the directions from the CSE docs to create a PKS Service Account to use to enable an OvDC for Enterprise PKS: ``` uaac client add --name cse-admin --scope uaa.none...

I have been working with a couple of partners recently that are looking to use CSE only to manage/deploy Enterprise PKS clusters. Both of these partners have PKS and vCD...

enhancement

Is it possible to create a separate dashboard in VROPs for vApps created using CSE (K8s cluster vms) ?

question

The following error is thrown when uploading the templates to VCD for a PKS configuration during 'cse install': [ df963ef4-fc2f-459b-8006-524077c343b9 ] Only direct vApp networks are allowed in Org VDC...

known issue

https://docs.vmware.com/en/vCloud-Director/10.0/com.vmware.vcloud.install.doc/GUID-84390C8F-E8C5-4137-A1A5-53EC27FE0024.html When you disable the Service Provider Access to the Legacy API Endpoint the CSE deamon can't start anymore. ``` root@cse [ ~ ]# cse run --config /root/cse/config.yaml Required Python...

known issue

Hi, We are in the process of deploying CSE - it seems lightweight enough that we have decided to run this on one of the vCD Cells. My understanding is...

question

After upgrading our Enterprise PKS 1.4.1 environment to 1.5.0, all of the existing k8 clusters are upgrading to a newer version of k8 and the "ACTION" state of the cluster...

bug