I'm attempting to use STS to generate a service token required for the Rancher Extension. Currently SUSE Observability uses the loadbalancer's default certificate. using --skip-ssl does not seem to resolve the issue
user@computer:~$ sts context save --url https://abc --api-token xx --skip-ssl
❌ Could not connect to https://abc (Get "https://abc/api/server/info": tls: failed to verify certificate: x509: certificate is valid for 94f892b4f4a29cfefb873a38152f2be6.1078642872067493c8c79d591f6fdf51.traefik.default, not ABC)
If I use --skip-validate, the context does save, and I am able to use --skip-ssl on other commands. It just doesn't appear to help inform the validation logic to skip-ssl as well.
I'm attempting to use STS to generate a service token required for the Rancher Extension. Currently SUSE Observability uses the loadbalancer's default certificate. using
--skip-ssldoes not seem to resolve the issueuser@computer:~$ sts context save --url https://abc --api-token xx --skip-ssl
❌ Could not connect to https://abc (Get "https://abc/api/server/info": tls: failed to verify certificate: x509: certificate is valid for 94f892b4f4a29cfefb873a38152f2be6.1078642872067493c8c79d591f6fdf51.traefik.default, not ABC)
If I use --skip-validate, the context does save, and I am able to use --skip-ssl on other commands. It just doesn't appear to help inform the validation logic to skip-ssl as well.