james.cooke

Hey bot. Just a bump to make sure this isn't closed as it should be a simple change and appears scheduled for development.

Hey bot. Just a bump to make sure this isn't closed as it should be a simple change and appears scheduled for development.

Hey bot. Just a bump to make sure this isn't closed as it should be a simple change and appears scheduled for development. (I'm not a bot, you are)

Another bump to make sure this isn't closed as it should be a simple change and appears scheduled for development.

Hi @apoorvajagtap - yes, that sounds very much like what we require. It's been a minute so I had to reach into the depths of my memory, but as it...

Hi @manno - how is the secret meant to be structured? I've tried a few variations, and no matter what I do the job/pods errors. ``` HOSTNAME=system-control-external-workloads-7bd38-rkd4r KUBERNETES_PORT_443_TCP_PROTO=tcp COMMIT=b942f*************************aedae14 KUBERNETES_PORT_443_TCP_ADDR=172.20.0.1...

Hi @0xavi0 - I have retested, being very careful to import/configure the secret using 'secrets-path.yaml' and the content structure as advised, and I can confirm this appears to be working...

Spec isn't required by default. If I create a very basic CRD then try and import the following: ```yaml apiVersion: mycrd.io/v1 kind: MyResource metadata: name: example namespace: default ``` it...