[K8s testing] Support use of Kustomize #1125

constanca-m · 2023-01-31T16:16:00Z

What

Support use of Kustomize to remove having to maintain KSM version according to the latest supported Kubernetes version. See more details in this issue.

Note: This change only affects the testing of Kubernetes integration. More information on this here.

Walk through

There are four steps to run the tests (check the code here):

Verify context.
Connect to the elastic stack network.
Install Elastic Agent.
Install custom definitions. These are present in the folder kubernetes/_dev/deploy/k8s.

Of these steps, manifests are being deployed through 3 and 4. However, step 3 does not use files from our custom definitions, and therefore, is not important for the specific testing files of Kubernetes integration.

To not install custom definitions, we need the presence of an .empty file. Taking apiserver datastream as an example, since we have the .empty file, nothing from kubernetes/_dev/deploy/k8s will be deployed.
On the other hand, state_cronjob datastream does not have that file, so custom definitions will be installed.

The main function responsible for applying the custom manifests is this one. This function is only used to deploy the custom definitions, not the elastic agent. So changing it won't affect anything related to it. Our specific goal to Kubernetes integration is to deploy the newest KSM version in an automated way, so we need to use a kustomization.yaml file to ensure that. This will stop requiring maintenance in regard to future KSM version. For that, we need to change our -f flag to -k flag.

To determine the correct path for the custom files we use this function, which is, once again, only used to installed custom definitions, so step 3 will not be affected. It will be refactored to:

Check if _dev/deploy/k8s directory given as argument exists. (Same as before)
Check if kustomization.yaml file exists: if it does not exist, then deploy the existent .yaml. manifests.

Outcome

If we update the custom definitions folder to have the right kustomization.yaml file - i.e. one that deploys kube state metrics and all the needed resources - the logs for each state_* datastream would be like this:

2023/01/31 16:58:01 DEBUG Running system tests for data stream
2023/01/31 16:58:01 DEBUG running test with configuration 'default'
2023/01/31 16:58:01 DEBUG setting up service...
2023/01/31 16:58:01 DEBUG ensure that kind context is selected
2023/01/31 16:58:01 DEBUG output command: /usr/local/bin/kubectl config current-context
2023/01/31 16:58:02 DEBUG find "kind-control-plane" container
2023/01/31 16:58:02 DEBUG output command: /usr/local/bin/docker ps --filter name=kind-control-plane --format {{.ID}}
2023/01/31 16:58:02 DEBUG check network connectivity between service container kind-control-plane (ID: 7765398977cd) and the stack network elastic-package-stack_default
2023/01/31 16:58:02 DEBUG output command: /usr/local/bin/docker network inspect elastic-package-stack_default
2023/01/31 16:58:02 DEBUG container kind-control-plane is already attached to the elastic-package-stack_default network
2023/01/31 16:58:02 DEBUG install Elastic Agent in the Kubernetes cluster
2023/01/31 16:58:02 DEBUG GET https://127.0.0.1:5601/api/status
2023/01/31 16:58:02 DEBUG Prepare YAML definition for Elastic Agent running in stack v8.6.0
2023/01/31 16:58:02 DEBUG Apply Kubernetes stdin
2023/01/31 16:58:02 DEBUG run command: /usr/local/bin/kubectl apply -f - -o yaml
2023/01/31 16:58:03 DEBUG Handle "apply" command output
2023/01/31 16:58:03 DEBUG Extract resources from command output
2023/01/31 16:58:03 DEBUG Wait for ready resources
2023/01/31 16:58:03 DEBUG Sync resource info: elastic-package-certs (kind: Secret, namespace: kube-system)
2023/01/31 16:58:03 DEBUG Sync resource info: elastic-agent (kind: DaemonSet, namespace: kube-system)
2023/01/31 16:58:03 DEBUG Sync resource info: elastic-agent (kind: ClusterRoleBinding, namespace: )
2023/01/31 16:58:03 DEBUG Sync resource info: elastic-agent (kind: RoleBinding, namespace: kube-system)
2023/01/31 16:58:03 DEBUG Sync resource info: elastic-agent-kubeadm-config (kind: RoleBinding, namespace: kube-system)
2023/01/31 16:58:03 DEBUG Sync resource info: elastic-agent (kind: ClusterRole, namespace: )
2023/01/31 16:58:03 DEBUG Sync resource info: elastic-agent (kind: Role, namespace: kube-system)
2023/01/31 16:58:03 DEBUG Sync resource info: elastic-agent-kubeadm-config (kind: Role, namespace: kube-system)
2023/01/31 16:58:03 DEBUG Sync resource info: elastic-agent (kind: ServiceAccount, namespace: kube-system)
2023/01/31 16:58:03 DEBUG beginning wait for 9 resources with timeout of 10m0s
2023/01/31 16:58:03 DEBUG install custom Kubernetes definitions (directory: /home/c/go/src/github.com/elastic/integrations/packages/kubernetes/_dev/deploy/k8s)
2023/01/31 16:58:03 DEBUG Apply Kubernetes custom definitions
2023/01/31 16:58:03 DEBUG run command: /usr/local/bin/kubectl apply -k /home/c/go/src/github.com/elastic/integrations/packages/kubernetes/_dev/deploy/k8s -o yaml
2023/01/31 16:58:05 DEBUG Handle "apply" command output
2023/01/31 16:58:05 DEBUG Extract resources from command output
2023/01/31 16:58:05 DEBUG Wait for ready resources
2023/01/31 16:58:05 DEBUG Sync resource info: pods-high (kind: ResourceQuota, namespace: default)
2023/01/31 16:58:05 DEBUG Sync resource info: kube-state-metrics (kind: ServiceAccount, namespace: kube-system)
2023/01/31 16:58:06 DEBUG Sync resource info: kube-state-metrics (kind: ClusterRole, namespace: )
2023/01/31 16:58:06 DEBUG Sync resource info: kube-state-metrics (kind: ClusterRoleBinding, namespace: )
2023/01/31 16:58:06 DEBUG Sync resource info: example-redis-config (kind: ConfigMap, namespace: default)
2023/01/31 16:58:06 DEBUG Sync resource info: kube-state-metrics (kind: Service, namespace: kube-system)
2023/01/31 16:58:06 DEBUG Sync resource info: task-pv-volume (kind: PersistentVolume, namespace: )
2023/01/31 16:58:06 DEBUG Sync resource info: task-pv-claim (kind: PersistentVolumeClaim, namespace: default)
2023/01/31 16:58:06 DEBUG Sync resource info: kube-state-metrics (kind: Deployment, namespace: kube-system)
2023/01/31 16:58:06 DEBUG Sync resource info: web (kind: StatefulSet, namespace: default)
2023/01/31 16:58:06 DEBUG Sync resource info: hello (kind: CronJob, namespace: default)
2023/01/31 16:58:06 DEBUG Sync resource info: fluentd-elasticsearch (kind: DaemonSet, namespace: kube-system)
2023/01/31 16:58:06 DEBUG Sync resource info: hello (kind: Job, namespace: default)
2023/01/31 16:58:06 DEBUG beginning wait for 13 resources with timeout of 10m0s
2023/01/31 16:58:06 DEBUG Deployment is not ready: kube-system/kube-state-metrics. 0 out of 1 expected pods are ready
2023/01/31 16:58:08 DEBUG Deployment is not ready: kube-system/kube-state-metrics. 0 out of 1 expected pods are ready
2023/01/31 16:58:10 DEBUG Deployment is not ready: kube-system/kube-state-metrics. 0 out of 1 expected pods are ready
2023/01/31 16:58:12 DEBUG Deployment is not ready: kube-system/kube-state-metrics. 0 out of 1 expected pods are ready
2023/01/31 16:58:14 DEBUG Deployment is not ready: kube-system/kube-state-metrics. 0 out of 1 expected pods are ready
2023/01/31 16:58:16 DEBUG StatefulSet is ready: default/web. 1 out of 1 expected pods are ready
2023/01/31 16:58:16 DEBUG creating test policy...
2023/01/31 16:58:16 DEBUG POST https://127.0.0.1:5601/api/fleet/agent_policies
2023/01/31 16:58:20 DEBUG adding package data stream to test policy...
2023/01/31 16:58:20 DEBUG POST https://127.0.0.1:5601/api/fleet/package_policies
2023/01/31 16:58:23 DEBUG deleting old data in data stream...
2023/01/31 16:58:23 DEBUG found 0 hits in metrics-kubernetes.state_storageclass-ep data stream
2023/01/31 16:58:23 DEBUG GET https://127.0.0.1:5601/api/fleet/agents
2023/01/31 16:58:23 DEBUG filter agents using criteria: NamePrefix=kind-control-plane
2023/01/31 16:58:23 DEBUG found 1 enrolled agent(s)
2023/01/31 16:58:23 DEBUG GET https://127.0.0.1:5601/api/fleet/agent_policies/134afa00-a180-11ed-be41-0b0968616500
2023/01/31 16:58:23 DEBUG assigning package data stream to agent...
2023/01/31 16:58:23 DEBUG PUT https://127.0.0.1:5601/api/fleet/agents/25fd07a7-522f-4399-af4d-c441b2867560/reassign
2023/01/31 16:58:25 DEBUG GET https://127.0.0.1:5601/api/fleet/agents/25fd07a7-522f-4399-af4d-c441b2867560
2023/01/31 16:58:25 DEBUG Agent data: {"id":"25fd07a7-522f-4399-af4d-c441b2867560","policy_id":"134afa00-a180-11ed-be41-0b0968616500","local_metadata":{"host":{"name":"kind-control-plane"}}}
2023/01/31 16:58:25 DEBUG Wait until the policy (ID: 134afa00-a180-11ed-be41-0b0968616500, revision: 2) is assigned to the agent (ID: 25fd07a7-522f-4399-af4d-c441b2867560)...
2023/01/31 16:58:27 DEBUG GET https://127.0.0.1:5601/api/fleet/agents/25fd07a7-522f-4399-af4d-c441b2867560
2023/01/31 16:58:27 DEBUG Agent data: {"id":"25fd07a7-522f-4399-af4d-c441b2867560","policy_id":"134afa00-a180-11ed-be41-0b0968616500","local_metadata":{"host":{"name":"kind-control-plane"}}}
2023/01/31 16:58:27 DEBUG Wait until the policy (ID: 134afa00-a180-11ed-be41-0b0968616500, revision: 2) is assigned to the agent (ID: 25fd07a7-522f-4399-af4d-c441b2867560)...
2023/01/31 16:58:29 DEBUG GET https://127.0.0.1:5601/api/fleet/agents/25fd07a7-522f-4399-af4d-c441b2867560
2023/01/31 16:58:29 DEBUG Agent data: {"id":"25fd07a7-522f-4399-af4d-c441b2867560","policy_id":"134afa00-a180-11ed-be41-0b0968616500","local_metadata":{"host":{"name":"kind-control-plane"}}}
2023/01/31 16:58:29 DEBUG Wait until the policy (ID: 134afa00-a180-11ed-be41-0b0968616500, revision: 2) is assigned to the agent (ID: 25fd07a7-522f-4399-af4d-c441b2867560)...
2023/01/31 16:58:31 DEBUG GET https://127.0.0.1:5601/api/fleet/agents/25fd07a7-522f-4399-af4d-c441b2867560
2023/01/31 16:58:31 DEBUG Agent data: {"id":"25fd07a7-522f-4399-af4d-c441b2867560","policy_id":"134afa00-a180-11ed-be41-0b0968616500","policy_revision":2,"local_metadata":{"host":{"name":"kind-control-plane"}}}
2023/01/31 16:58:31 DEBUG Policy revision assigned to the agent (ID: 25fd07a7-522f-4399-af4d-c441b2867560)...
2023/01/31 16:58:31 DEBUG checking for expected data in data stream...
2023/01/31 16:58:31 DEBUG found 0 hits in metrics-kubernetes.state_storageclass-ep data stream
2023/01/31 16:58:32 DEBUG found 0 hits in metrics-kubernetes.state_storageclass-ep data stream
2023/01/31 16:58:33 DEBUG found 0 hits in metrics-kubernetes.state_storageclass-ep data stream
2023/01/31 16:58:34 DEBUG found 1 hits in metrics-kubernetes.state_storageclass-ep data stream
2023/01/31 16:58:34 DEBUG reassigning original policy back to agent...
2023/01/31 16:58:34 DEBUG PUT https://127.0.0.1:5601/api/fleet/agents/25fd07a7-522f-4399-af4d-c441b2867560/reassign
2023/01/31 16:58:36 DEBUG GET https://127.0.0.1:5601/api/fleet/agents/25fd07a7-522f-4399-af4d-c441b2867560
2023/01/31 16:58:36 DEBUG Agent data: {"id":"25fd07a7-522f-4399-af4d-c441b2867560","policy_id":"elastic-agent-managed-ep","local_metadata":{"host":{"name":"kind-control-plane"}}}
2023/01/31 16:58:36 DEBUG Wait until the policy (ID: elastic-agent-managed-ep, revision: 3) is assigned to the agent (ID: 25fd07a7-522f-4399-af4d-c441b2867560)...
2023/01/31 16:58:38 DEBUG GET https://127.0.0.1:5601/api/fleet/agents/25fd07a7-522f-4399-af4d-c441b2867560
2023/01/31 16:58:38 DEBUG Agent data: {"id":"25fd07a7-522f-4399-af4d-c441b2867560","policy_id":"elastic-agent-managed-ep","local_metadata":{"host":{"name":"kind-control-plane"}}}
2023/01/31 16:58:38 DEBUG Wait until the policy (ID: elastic-agent-managed-ep, revision: 3) is assigned to the agent (ID: 25fd07a7-522f-4399-af4d-c441b2867560)...
2023/01/31 16:58:40 DEBUG GET https://127.0.0.1:5601/api/fleet/agents/25fd07a7-522f-4399-af4d-c441b2867560
2023/01/31 16:58:40 DEBUG Agent data: {"id":"25fd07a7-522f-4399-af4d-c441b2867560","policy_id":"elastic-agent-managed-ep","local_metadata":{"host":{"name":"kind-control-plane"}}}
2023/01/31 16:58:40 DEBUG Wait until the policy (ID: elastic-agent-managed-ep, revision: 3) is assigned to the agent (ID: 25fd07a7-522f-4399-af4d-c441b2867560)...
2023/01/31 16:58:42 DEBUG GET https://127.0.0.1:5601/api/fleet/agents/25fd07a7-522f-4399-af4d-c441b2867560
2023/01/31 16:58:42 DEBUG Agent data: {"id":"25fd07a7-522f-4399-af4d-c441b2867560","policy_id":"elastic-agent-managed-ep","local_metadata":{"host":{"name":"kind-control-plane"}}}
2023/01/31 16:58:42 DEBUG Wait until the policy (ID: elastic-agent-managed-ep, revision: 3) is assigned to the agent (ID: 25fd07a7-522f-4399-af4d-c441b2867560)...
2023/01/31 16:58:44 DEBUG GET https://127.0.0.1:5601/api/fleet/agents/25fd07a7-522f-4399-af4d-c441b2867560
2023/01/31 16:58:44 DEBUG Agent data: {"id":"25fd07a7-522f-4399-af4d-c441b2867560","policy_id":"elastic-agent-managed-ep","policy_revision":3,"local_metadata":{"host":{"name":"kind-control-plane"}}}
2023/01/31 16:58:44 DEBUG Policy revision assigned to the agent (ID: 25fd07a7-522f-4399-af4d-c441b2867560)...
2023/01/31 16:58:44 DEBUG deleting test policy...
2023/01/31 16:58:44 DEBUG POST https://127.0.0.1:5601/api/fleet/agent_policies/delete
2023/01/31 16:58:47 DEBUG tearing down service...
2023/01/31 16:58:47 DEBUG uninstall custom Kubernetes definitions (directory: /home/c/go/src/github.com/elastic/integrations/packages/kubernetes/_dev/deploy/k8s)
2023/01/31 16:58:47 DEBUG run command: /usr/local/bin/kubectl delete -k /home/c/go/src/github.com/elastic/integrations/packages/kubernetes/_dev/deploy/k8s
2023/01/31 16:58:49 DEBUG deleting data in data stream...

Related issues

Closes [K8s testing] Support use of Kustomize #1102

elasticmachine · 2023-01-31T16:35:03Z

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2023-02-09T09:58:11.119+0000
Duration: 33 min 17 sec

Test stats 🧪

Test	Results
Failed	0
Passed	888
Skipped	0
Total	888

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

elasticmachine · 2023-01-31T17:00:24Z

🌐 Coverage report

Name	Metrics % (`covered/total`)	Diff
Packages	100.0% (`35/35`)	💚
Files	65.909% (`87/132`)	👍
Classes	61.376% (`116/189`)	👍
Methods	49.146% (`403/820`)	👍 0.375
Lines	31.767% (`3576/11257`)	👎 -0.006
Conditionals	100.0% (`0/0`)	💚

internal/testrunner/runners/system/servicedeployer/kubernetes.go

docs/howto/system_testing.md

internal/testrunner/runners/system/servicedeployer/kubernetes.go

tetianakravchenko

I still don't think that should be enforced usage of kustomization.yaml, if manually defined manifests stored in _dev/deploy/k8s covers all needs and there is no reason to use kustomization.yml - this should be supported
I think you also need to update https://github.com/elastic/elastic-package/tree/main/test/packages/with-kind/kubernetes with accordance with your changes

constanca-m · 2023-02-06T15:54:55Z

I still don't think that should be enforced usage of kustomization.yaml, if manually defined manifests stored in _dev/deploy/k8s covers all needs and there is no reason to use kustomization.yml - this should be supported

But what is the reason for that? It seems unnecessary. This is used just for testing, so once there, it doesn't really matter what happens next. And since at this moment, Kubernetes integration is the only one that uses this, it is an easy way to change system testing as we won't need to spread this change to any other package. @tetianakravchenko

tetianakravchenko · 2023-02-07T09:10:42Z

   I still don't think that should be enforced usage of kustomization.yaml, if manually defined manifests stored in _dev/deploy/k8s covers all needs and there is no reason to use kustomization.yml - this should be supported
But what is the reason for that? It seems unnecessary. This is used just for testing, so once there, it doesn't really matter what happens next. And since at this moment, Kubernetes integration is the only one that uses this, it is an easy way to change system testing as we won't need to spread this change to any other package. @tetianakravchenko

yes, Kubernetes integration is the only one that uses it, but I don't think that it implies that this should be enforced for other integrations, that are not using those tests yet (like cloud_defend and cloud_security_posture), I see it more like an alternative

I think you also need to update https://github.com/elastic/elastic-package/tree/main/test/packages/with-kind/kubernetes with accordance with your changes

@constanca-m also wdyt about this? namely content of https://github.com/elastic/elastic-package/tree/main/test/packages/with-kind/kubernetes/_dev/deploy/k8s to align with your changes?

constanca-m · 2023-02-07T09:23:41Z

yes, Kubernetes integration is the only one that uses it, but I don't think that it implies that this should be enforced for other integrations, that are not using those tests yet (like cloud_defend and cloud_security_posture), I see it more like an alternative

They are using the .empty file so they don't require any changes.

@constanca-m also wdyt about this? namely content of https://github.com/elastic/elastic-package/tree/main/test/packages/with-kind/kubernetes/_dev/deploy/k8s to align with your changes?

I hadn't notice that, but the datastream being used for testing has the .empty file so we were not testing the custom definitions. I will update it to include the new resources + one more data stream to check the kustomization.yaml file. @tetianakravchenko

tetianakravchenko · 2023-02-07T09:39:59Z

They are using the .empty file so they don't require any changes.

ok, lets iterate over it

I hadn't notice that, but the datastream being used for testing has the .empty file so we were not testing the custom definitions. I will update it to include the new resources + one more data stream to check the kustomization.yaml file. @tetianakravchenko

hmm, maybe I misunderstood the purpose of this test folder. But I think it is good to have an example in this repo of the package with kustomization.yaml

constanca-m · 2023-02-07T09:41:22Z

hmm, maybe I misunderstood the purpose of this test folder. But I think it is good to have an example in this repo of the package with kustomization.yaml

You got it right, that folder is being used for testing. The tests were not covering the two cases before, but now they are.

gsantoro · 2023-02-07T10:04:21Z

test/packages/with-kind/kubernetes/_dev/deploy/k8s/daemonset.yaml

@@ -0,0 +1,48 @@
+apiVersion: apps/v1
+kind: DaemonSet
+metadata:


where is this daemonset.yaml coming from?

We need these resources to check the state_* datastreams, but since I only included one for the pod, maybe I should delete all the others? I was trying to follow the same logic as the one that was here before.

where is this daemonset.yaml coming from?

@gsantoro it is the same as used in integrations repo - https://github.com/elastic/integrations/blob/main/packages/kubernetes/_dev/deploy/k8s/daemonset.yaml

I am torn between deleting some of the resources because they are useless, or keeping them so they stay the same as in the integrations repo

let me see if I understand.

you are adding a state_pod datastream here since pod didn't even need the kube-state-metrics resource that was already defined in those manifests resources (before the kustomization was introduced). those resources in deploy/k8s are in theory used to setup the environment for testing but since we don't check for output against an expected result, they are kind of useless. we only check that the setup didn't have any issues.

I would say, keep them in sync with what we are doing in the integrations repo. it's definitively another PR

Yes, they were useless before because the only data stream defined had the .empty file. They are no longer useless.

tetianakravchenko · 2023-02-07T10:20:09Z

@constanca-m please double check with @elastic/ecosystem team regarding failing buildkite/elastic-package before merging

constanca-m · 2023-02-07T10:33:04Z

@constanca-m please double check with @elastic/ecosystem team regarding failing buildkite/elastic-package before merging

I don't think the error is related to any change of this PR @tetianakravchenko

gsantoro · 2023-02-07T10:37:28Z

@tetianakravchenko I checked that error yesterday. The pipeline has not been setup entirely. I would say that we should notify them. At the same time I expect them to reply they haven't created one yet and they have enabled that step on all the repos automatically.

constanca-m · 2023-02-07T10:40:59Z

@tetianakravchenko @gsantoro The error is more specific than the screenshot yesterday:

Deprecated Environment Variables

The following environment variables have been deprecated, and should no longer be used:

BUILDKITE_PROJECT_SLUG="elastic/elastic-package"
BUILDKITE_PROJECT_PROVIDER="github"

But it seems that this should be a different PR. I tried to find these variables specific to this change, but I don't think they exist.

gsantoro · 2023-02-07T10:45:34Z

@constanca-m actually the pipeline is now there at https://buildkite.com/elastic/elastic-package.

I think you need to rebase from upstream to get the builkite pipeline definition at

elastic-package/.buildkite/pipeline.yml

Line 4 in 8c85a68

agents:

constanca-m · 2023-02-07T10:47:40Z

@constanca-m actually the pipeline is now there at https://buildkite.com/elastic/elastic-package

That's for every run, but if you check the error of the specific cause of this PR, that is the log that appears. @gsantoro

mlunadia · 2023-02-07T11:39:44Z

@constanca-m is this linked to this epic?

constanca-m · 2023-02-07T11:49:38Z

@constanca-m is this linked to this epic?

I wouldn't say so @mlunadia. KSM was already being deployed, this change is just so we don't have to update the version every time we support a new version of K8s.

jsoriano

This looks like a breaking change, and it looks feasible to keep backwards compatibility by checking if kustomize is used or not. Could we do it?

Please correct me if this will work with current packages.

docs/howto/system_testing.md

test/packages/with-kind/kubernetes/_dev/deploy/k8s/kustomization.yaml

internal/testrunner/runners/system/servicedeployer/kubernetes.go

jsoriano · 2023-02-07T17:49:23Z

internal/testrunner/runners/system/servicedeployer/kubernetes.go

+		// if it does not exist, then the .empty file needs to be present
+		if _, err := os.Stat(filepath.Join(definitionsPath, ".empty")); err != nil {
+			return false, errors.Errorf("kustomization.yaml file is missing (path: %s). Add one or create an .empty file"+
+				" if no custom definitions are required.", definitionsPath)


If we require certain files to be present, it would be better to make these checks on the package-spec.

test/packages/with-kind/kubernetes/_dev/deploy/k8s/kustomization.yaml

ChrsMark · 2023-02-09T07:49:04Z

test/packages/with-kind/kubernetes/data_stream/state_cronjob/fields/agent.yml

@@ -0,0 +1,198 @@
+- name: cloud


Since it's only for testing, could we reduce the amount of fields we have in this file?

We can, but it was left as it is to be in sync with Kubernetes integration. Should I update it?

jsoriano

Thanks for the updates to avoid the breaking change!

docs/howto/system_testing.md

internal/kubectl/kubectl.go

test/packages/with-kind/kubernetes/_dev/deploy/k8s/kustomization.yaml

No blockers on sight.

jsoriano

👍

constanca-m added 4 commits January 16, 2023 15:50

Add support for 1.26 K8s version. Update kind version.

c3166f0

Merge remote-tracking branch 'origin/main'

0810db7

Merge remote-tracking branch 'origin/main'

e8e438e

Add support for kustomize.

9997299

constanca-m self-assigned this Jan 31, 2023

constanca-m added the Team:Cloudnative-Monitoring Label for the Cloud Native Monitoring team label Jan 31, 2023

constanca-m requested review from gizas, gsantoro and tetianakravchenko January 31, 2023 16:17

Fix doc.

090b606

gsantoro suggested changes Feb 6, 2023

View reviewed changes

constanca-m added 2 commits February 6, 2023 11:10

Fix function and variable names.

9bcb14a

Fix how to.

15e5d6f

constanca-m requested a review from gsantoro February 6, 2023 10:13

gsantoro suggested changes Feb 6, 2023

View reviewed changes

constanca-m requested a review from gsantoro February 6, 2023 13:39

constanca-m added 2 commits February 6, 2023 15:28

Fix function name.

a8f0728

Fix function readability.

b335a8e

tetianakravchenko reviewed Feb 6, 2023

View reviewed changes

Update README

7139df0

constanca-m requested a review from tetianakravchenko February 6, 2023 17:00

gsantoro approved these changes Feb 6, 2023

View reviewed changes

Update testing with kind.

e4d5853

tetianakravchenko requested a review from a team February 7, 2023 09:33

Update manifest.

69f1415

gsantoro reviewed Feb 7, 2023

View reviewed changes

tetianakravchenko approved these changes Feb 7, 2023

View reviewed changes

Merge branch 'elastic:main' into apply-k

3dd7a11

MichaelKatsoulis requested a review from jsoriano February 7, 2023 12:02

jsoriano previously requested changes Feb 7, 2023

View reviewed changes

Fix references.

0924619

jsoriano reviewed Feb 8, 2023

View reviewed changes

test/packages/with-kind/kubernetes/_dev/deploy/k8s/kustomization.yaml Show resolved Hide resolved

constanca-m added 3 commits February 8, 2023 11:04

Make -f possible along with -k

1fc8992

Fix import cycle.

86bcaf2

Fix kustomization.yaml file path.

2452a9e

constanca-m requested a review from jsoriano February 8, 2023 11:02

ChrsMark reviewed Feb 9, 2023

View reviewed changes

jsoriano reviewed Feb 9, 2023

View reviewed changes

docs/howto/system_testing.md Show resolved Hide resolved

internal/kubectl/kubectl.go Show resolved Hide resolved

test/packages/with-kind/kubernetes/_dev/deploy/k8s/kustomization.yaml Show resolved Hide resolved

Update system_testing.md

a1512f6

jsoriano approved these changes Feb 9, 2023

View reviewed changes

constanca-m merged commit ab4357c into elastic:main Feb 9, 2023

constanca-m deleted the apply-k branch February 9, 2023 10:32

constanca-m mentioned this pull request Feb 9, 2023

[Kubernetes] Update system testing manifests elastic/integrations#5227

Merged

4 tasks

constanca-m mentioned this pull request Oct 4, 2023

[K8s testing] Support use of Kustomize #1102

Closed

[K8s testing] Support use of Kustomize #1125

[K8s testing] Support use of Kustomize #1125

Uh oh!

Conversation

constanca-m commented Jan 31, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What

Walk through

Outcome

Related issues

Uh oh!

elasticmachine commented Jan 31, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

💚 Build Succeeded

Build stats

Test stats 🧪

🤖 GitHub comments

Uh oh!

elasticmachine commented Jan 31, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🌐 Coverage report

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

tetianakravchenko left a comment

Choose a reason for hiding this comment

Uh oh!

constanca-m commented Feb 6, 2023

Uh oh!

tetianakravchenko commented Feb 7, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

constanca-m commented Feb 7, 2023

Uh oh!

tetianakravchenko commented Feb 7, 2023

Uh oh!

constanca-m commented Feb 7, 2023

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

tetianakravchenko commented Feb 7, 2023

Uh oh!

constanca-m commented Feb 7, 2023

Uh oh!

gsantoro commented Feb 7, 2023

Uh oh!

constanca-m commented Feb 7, 2023

Uh oh!

gsantoro commented Feb 7, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

constanca-m commented Feb 7, 2023

Uh oh!

mlunadia commented Feb 7, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

constanca-m commented Feb 7, 2023

Uh oh!

jsoriano left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

constanca-m commented Jan 31, 2023 •

edited

Loading

elasticmachine commented Jan 31, 2023 •

edited

Loading

elasticmachine commented Jan 31, 2023 •

edited

Loading

tetianakravchenko commented Feb 7, 2023 •

edited

Loading

gsantoro commented Feb 7, 2023 •

edited

Loading

mlunadia commented Feb 7, 2023 •

edited

Loading