NOTE: passing --output to the kubectl hlf ca create outputs correct values.
Even when manually modifying the FabricCA CRD resource with the gateway values does not work. Lens shows the CRD as updated, but further inspection show that the gateway values are missing.
What did you expect to happen?
I expect the kubectl hlf ca create command to create the TSLRoute CRD.
How can we reproduce it (as minimally and precisely as possible)?
1.7259154457291129e+09 INFO controllers.FabricCA purge requested for org1-ca
1.7259154458758335e+09 INFO controllers.FabricCA CA resource not found. Ignoring since object must be deleted. {"hlf": "wekeo-eo-dev/org1-ca"}
1.7259155556021981e+09 INFO controllers.FabricCA Adding Finalizer for the CA {"hlf": "XXXXXX/org1-ca"}
1.7259155566638715e+09 INFO controllers.FabricCA creating 10 resource(s)
1.7259155570278666e+09 INFO controllers.FabricCA preparing upgrade for org1-ca
1.7259155579421625e+09 INFO controllers.FabricCA performing update for org1-ca
1.7259155582418983e+09 INFO controllers.FabricCA creating upgraded release for org1-ca
1.7259155582697067e+09 INFO controllers.FabricCA checking 10 resources for changes
1.7259155582748258e+09 INFO controllers.FabricCA Patch Secret "org1-ca--ca" in namespace default
1.725915558285192e+09 INFO controllers.FabricCA Looks like there are no changes for Secret "org1-ca--msp-cryptomaterial"
1.7259155582936523e+09 INFO controllers.FabricCA Looks like there are no changes for Secret "org1-ca--msp-tls-cryptomaterial"
1.7259155583350508e+09 INFO controllers.FabricCA Looks like there are no changes for Secret "org1-ca--tls-cryptomaterial"
1.7259155583456178e+09 INFO controllers.FabricCA Looks like there are no changes for ConfigMap "org1-ca--ca"
1.7259155583572245e+09 INFO controllers.FabricCA Looks like there are no changes for ConfigMap "org1-ca--config-tls"
1.7259155583692648e+09 INFO controllers.FabricCA Looks like there are no changes for ConfigMap "org1-ca--config"
1.725915558376979e+09 INFO controllers.FabricCA Looks like there are no changes for PersistentVolumeClaim "org1-ca"
1.725915558384629e+09 INFO controllers.FabricCA Looks like there are no changes for Service "org1-ca"
1.725915558394765e+09 INFO controllers.FabricCA Patch Deployment "org1-ca" in namespace default
1.7259155584249196e+09 INFO controllers.FabricCA updating status for upgraded release for org1-ca
time="2024-09-09T20:59:18Z" level=info msg="CA org1-ca in pending status, refreshing state in 10 seconds"
1.725915558509569e+09 INFO controllers.FabricCA preparing upgrade for org1-ca
1.725915559445631e+09 INFO controllers.FabricCA performing update for org1-ca
What happened?
I ran
The
FabricCA
CRD resource was created, but it's missing the Gateway API values such as:NOTE: passing
--output
to thekubectl hlf ca create
outputs correct values.Even when manually modifying the FabricCA CRD resource with the gateway values does not work. Lens shows the CRD as updated, but further inspection show that the gateway values are missing.
What did you expect to happen?
I expect the
kubectl hlf ca create
command to create the TSLRoute CRD.How can we reproduce it (as minimally and precisely as possible)?
Install traefik, with Gateway API enabled:
Anything else we need to know?
contoller logs
Kubernetes version