We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
cloud-on-k8s/pkg/controller/apmserver/config.go
Line 30 in f826719
ECK is setting outdated configuration for the APM secret token, that was removed in APM Server 8.0 (https://www.elastic.co/guide/en/apm/guide/current/release-notes-8.0.html#_breaking_changes_7). This should be updated to apm-server.auth.secret_token for 8.0+
apm-server.auth.secret_token
The outcome of this bug is that, by default, APM Server has no secret token auth configured.
The text was updated successfully, but these errors were encountered:
@barkbay I think we should try to fix this for the upcoming 2.8 release wdyt?
Sorry, something went wrong.
Yes 👀
pebrc
Successfully merging a pull request may close this issue.
cloud-on-k8s/pkg/controller/apmserver/config.go
Line 30 in f826719
ECK is setting outdated configuration for the APM secret token, that was removed in APM Server 8.0 (https://www.elastic.co/guide/en/apm/guide/current/release-notes-8.0.html#_breaking_changes_7). This should be updated to
apm-server.auth.secret_token
for 8.0+The outcome of this bug is that, by default, APM Server has no secret token auth configured.
The text was updated successfully, but these errors were encountered: