Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enabling SSL caused relay-agent registration to fail. #243

Closed
britslampe opened this issue Aug 3, 2023 · 2 comments
Closed

Enabling SSL caused relay-agent registration to fail. #243

britslampe opened this issue Aug 3, 2023 · 2 comments
Labels
needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@britslampe
Copy link

Before following the instructions from Enabling SSL in Paralus I was able to import clusters to projects I have created on the console. But after it was enabled, I cannot import new clusters. I used cert-manager to generate the certificate and use Okta SSO to login.

I checked the pod logs for the relay-agent for both a cluster that is already imported and one I am trying (and failing) to import. The error is Method Not Allowed.

[POST /v2/sentry/bootstrap/{templateToken}/register][501] Bootstrap_RegisterBootstrapAgent default  &{Code:12 Details:[] Message:Method Not Allowed}
{"level":"error","ts":"2023-08-03T19:36:29.611Z","caller":"agent/agent.go:397","msg":"Relay Agent::failed to register relay agent error: [POST /v2/sentry/bootstrap/{templateToken}/register][501] Bootstrap_RegisterBootstrapAgent default  &{Code:12 Details:[] Message:Method Not Allowed}  ","stacktrace":"github.com/paralus/relay/pkg/agent.registerRelayAgent\n\t/build/pkg/agent/agent.go:397\ngithub.com/paralus/relay/pkg/agent.handleRelayNetworks\n\t/build/pkg/agent/agent.go:606"}
{"level":"info","ts":"2023-08-03T19:36:34.130Z","caller":"agent/agent.go:394","msg":"Relay Agent::config: &{TemplateToken:******************** TemplateName: Scheme: Mode: Addr:console.*******.***:80 ClientID:******************** ClientIP:**.***.**.** Name:relay-agent-*-* PrivateKey:[] CSR:[] Certificate:[] CACertificate:[] ServerHost: ServerPort:0 Fingerprint:*} "}

Note: I am able to use the kubectl session window to make changes still to the imported clusters even with these errors.

I found this similar issue, where a self-signed cert was being used, but in my case I am using cert-manager. #99 (comment)

Would removing the certificate, importing the clusters, then requesting a new certificate be a workaround for this?

@britslampe britslampe added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Aug 3, 2023
@britslampe
Copy link
Author

I am using v0.2.2 and have used jsonnet mapper for v0.2.1 as outlined in this change https://github.com/paralus/paralus/pull/211/files

@britslampe
Copy link
Author

Closing, referenced this original issue in the relay issue #76.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

1 participant