elastic-agent manifests: add comments; add cloudnative team as a codeowner for the k8s manifests #708
There are no files selected for viewing
Validating CODEOWNERS rules …
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,2 +1,4 @@ | ||
| # Team responsible for Fleet Server | ||
| * @elastic/elastic-agent-control-plane | ||
|
|
||
| /deploy/kubernetes @elastic/obs-cloudnative-monitoring | ||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,3 +1,4 @@ | ||
| # For more information refer to https://www.elastic.co/guide/en/fleet/current/running-on-kubernetes-managed-by-fleet.html | ||
| apiVersion: apps/v1 | ||
| kind: DaemonSet | ||
| metadata: | ||
|
|
@@ -14,34 +15,41 @@ spec: | |
| labels: | ||
| app: elastic-agent | ||
| spec: | ||
| # Tolerations are needed to run Elastic Agent on Kubernetes master nodes. | ||
| # Agents running on master nodes collect metrics from the control plane components (scheduler, controller manager) of Kubernetes | ||
| tolerations: | ||
| - key: node-role.kubernetes.io/master | ||
| effect: NoSchedule | ||
| serviceAccountName: elastic-agent | ||
| hostNetwork: true | ||
| # 'hostPID: true' enables the Elastic Security integration to observe all process exec events on the host. | ||
| # Sharing the host process ID namespace gives visibility of all processes running on the same host. | ||
| hostPID: true | ||
| dnsPolicy: ClusterFirstWithHostNet | ||
| containers: | ||
| - name: elastic-agent | ||
| image: docker.elastic.co/beats/elastic-agent:8.3.0 | ||
| env: | ||
| # Set to 1 for enrollment into Fleet server. If not set, Elastic Agent is run in standalone mode | ||
| - name: FLEET_ENROLL | ||
| value: "1" | ||
| # Set to true to communicate with Fleet with either insecure HTTP or unverified HTTPS | ||
| - name: FLEET_INSECURE | ||
| value: "true" | ||
| # Fleet Server URL to enroll the Elastic Agent into | ||
| # FLEET_URL can be found in Kibana, go to Management > Fleet > Settings | ||
| - name: FLEET_URL | ||
| value: "https://fleet-server:8220" | ||
| # Elasticsearch API key used to enroll Elastic Agents in Fleet (https://www.elastic.co/guide/en/fleet/current/fleet-enrollment-tokens.html#fleet-enrollment-tokens) | ||
| # If FLEET_ENROLLMENT_TOKEN is empty then KIBANA_HOST, KIBANA_FLEET_USERNAME, KIBANA_FLEET_PASSWORD are needed | ||
| - name: FLEET_ENROLLMENT_TOKEN | ||
| value: "" | ||
| - name: KIBANA_HOST | ||
| value: "http://kibana:5601" | ||
| # The basic authentication username used to connect to Kibana and retrieve a service_token to enable Fleet | ||
| - name: KIBANA_FLEET_USERNAME | ||
|
There was a problem hiding this comment. Do we need a link to direct users where to find those values? There was a problem hiding this comment. If you mean the service_token to enable Fleet, agent gets them automatically from Kibana when connected There was a problem hiding this comment. In managed yes. Maybe was not the best place to put the comment. But you get my point, that all of this values are somewhere in the portal and user needs point of reference. If makes sense. There was a problem hiding this comment. I've added info for FLEET_URL and enrollment token - d9c4344. Regarding KIBANA_*: it depends on the setup - elastic cloud or self-managed and I couldn't find a generic documentation |
||
| value: "elastic" | ||
| # The basic authentication password used to connect to Kibana and retrieve a service_token to enable Fleet | ||
| - name: KIBANA_FLEET_PASSWORD | ||
| value: "changeme" | ||
| - name: NODE_NAME | ||
|
|
@@ -104,21 +112,28 @@ spec: | |
| - name: varlog | ||
| hostPath: | ||
| path: /var/log | ||
| # Needed for cloudbeat | ||
| - name: etc-kubernetes | ||
| hostPath: | ||
| path: /etc/kubernetes | ||
| # Needed for cloudbeat | ||
| - name: var-lib | ||
| hostPath: | ||
| path: /var/lib | ||
| # Needed for cloudbeat | ||
| - name: passwd | ||
| hostPath: | ||
| path: /etc/passwd | ||
| # Needed for cloudbeat | ||
| - name: group | ||
| hostPath: | ||
| path: /etc/group | ||
| # Needed for cloudbeat | ||
| - name: etcsysmd | ||
| hostPath: | ||
| path: /etc/systemd | ||
| # Mount /etc/machine-id from the host to determine host ID | ||
| # Needed for Elastic Security integration | ||
| - name: etc-mid | ||
| hostPath: | ||
| path: /etc/machine-id | ||
|
|
@@ -180,6 +195,7 @@ rules: | |
| - pods | ||
| - services | ||
| - configmaps | ||
| # Needed for cloudbeat | ||
|
There was a problem hiding this comment. Either keep Needed or Required to have all lines aligned There was a problem hiding this comment. done df21c4c |
||
| - serviceaccounts | ||
| - persistentvolumes | ||
| - persistentvolumeclaims | ||
|
|
@@ -211,18 +227,20 @@ rules: | |
| - jobs | ||
| - cronjobs | ||
| verbs: [ "get", "list", "watch" ] | ||
| # Needed for apiserver | ||
| - nonResourceURLs: | ||
| - "/metrics" | ||
| verbs: | ||
| - get | ||
| # Needed for cloudbeat | ||
| - apiGroups: ["rbac.authorization.k8s.io"] | ||
| resources: | ||
| - clusterrolebindings | ||
| - clusterroles | ||
| - rolebindings | ||
| - roles | ||
| verbs: ["get", "list", "watch"] | ||
| # Needed for cloudbeat | ||
| - apiGroups: ["policy"] | ||
| resources: | ||
| - podsecuritypolicies | ||
|
|
@@ -232,7 +250,7 @@ apiVersion: rbac.authorization.k8s.io/v1 | |
| kind: Role | ||
| metadata: | ||
| name: elastic-agent | ||
| # Should be the namespace where elastic-agent is running | ||
| namespace: kube-system | ||
| labels: | ||
| k8s-app: elastic-agent | ||
|
|
||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@elastic/elastic-agent-control-plane I am getting error:
who could help me to get write access to this repo?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@andresrc this is the one talking about. Is there any docs mentioning the process to change this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@gizas @tetianakravchenko All employees are have write access to this repository, but probably in order to add the group to
CODEOWNERSthe group itself need to be explicitly added. I have just done that. Please let me know if it works.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, it works, now getting:
This CODEOWNERS file is valid.