-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Creation of Package Policies through API dont work for complex policy sample #138743
Labels
bug
Fixes for quality problems that affect the customer experience
Team:Fleet
Team label for Observability Data Collection Fleet team
Comments
Pinging @elastic/fleet (Team:Fleet) |
Related to #132263 |
@gizas the following request worked on my side I removed the
|
@nchaulet Works!!!!!!! thank you so much |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Fixes for quality problems that affect the customer experience
Team:Fleet
Team label for Observability Data Collection Fleet team
Kibana version:
8.3.2
Elasticsearch version:
8.3.2
Server OS version:
Browser version:
Chrome 104.0.5112.79
Browser OS version:
Version 104.0.5112.79 (Official Build) (arm64)
Original install method (e.g. download page, yum, from source, etc.):
Elastic Cloud
Describe the bug:
I am using the Fleet/Documentation API commands of given doc https://docs.google.com/document/d/1HP_UJQ8ntQijzagH4R-B8hSP3MDPwpVEHv0s54ysu8Q
Goal is to install the kubernetes Integration package inside a given Agent.
For the moment I have managed to authenticate to Elastic Cloud with following api config
My commands are successfull for installing nginx and also the package_policy given in the example.
Now I am trying to install following complex package policy:
k8spolicy.json.txt
Command:
But no error is produced and even nothing when I try -vvv verbose output.
Can you please help me troubleshoot and create package policy for k8s integration?
Agent with "policy_id": "d42d3030-1a3a-11ed-bda0-8feb86b4d5f6" already exists in my cluster
Steps to reproduce:
The text was updated successfully, but these errors were encountered: