Update dependency on elastic-package v0.28.0

[mtojek]

This PR bumps up dependency on elastic-package to v0.28.0.

Needed by: #2041

[elasticmachine]

💔 Tests Failed

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: 2021-11-03T12:32:07.236+0000

• Duration: 92 min 29 sec

• Commit: c97e686

Test stats 🧪

Test	Results
Failed	15
Passed	3270
Skipped	5
Total	3290

Test errors

Expand to view the tests failures

> Show only the first 10 test failures

Check integrations / kubernetes / kubernetes: check / system test: default – kubernetes.controllermanager

• no error details
Expand to view the stacktrace

 could not find hits in metrics-kubernetes.controllermanager-ep data stream 

Check integrations / kubernetes / kubernetes: check / system test: default – kubernetes.state_pod

• no error details
Expand to view the stacktrace

 one or more errors found in documents stored in metrics-kubernetes.state_pod-ep data stream: [0] found error.message in event: field [kubernetes.namespace.name] already exists 

Check integrations / kubernetes / kubernetes: check / system test: default – kubernetes.state_replicaset

• no error details
Expand to view the stacktrace

 one or more errors found in documents stored in metrics-kubernetes.state_replicaset-ep data stream: [0] found error.message in event: field [kubernetes.namespace.name] already exists 

Check integrations / kubernetes / kubernetes: check / system test: default – kubernetes.pod

• no error details
Expand to view the stacktrace

 one or more errors found in documents stored in metrics-kubernetes.pod-ep data stream: [0] found error.message in event: field [kubernetes.namespace.name] already exists 

Check integrations / kubernetes / kubernetes: check / system test: default – kubernetes.state_daemonset

• no error details
Expand to view the stacktrace

 one or more errors found in documents stored in metrics-kubernetes.state_daemonset-ep data stream: [0] found error.message in event: field [kubernetes.namespace.name] already exists 

Check integrations / kubernetes / kubernetes: check / system test: default – kubernetes.state_deployment

• no error details
Expand to view the stacktrace

 one or more errors found in documents stored in metrics-kubernetes.state_deployment-ep data stream: [0] found error.message in event: field [kubernetes.namespace.name] already exists 

Check integrations / kubernetes / kubernetes: check / system test: default – kubernetes.state_persistentvolumeclaim

• no error details
Expand to view the stacktrace

 one or more errors found in documents stored in metrics-kubernetes.state_persistentvolumeclaim-ep data stream: [0] found error.message in event: field [kubernetes.namespace.name] already exists 

Check integrations / kubernetes / kubernetes: check / system test: default – kubernetes.scheduler

• no error details
Expand to view the stacktrace

 could not find hits in metrics-kubernetes.scheduler-ep data stream 

Check integrations / kubernetes / kubernetes: check / system test: default – kubernetes.state_cronjob

• no error details
Expand to view the stacktrace

 one or more errors found in documents stored in metrics-kubernetes.state_cronjob-ep data stream: [0] found error.message in event: field [kubernetes.namespace.name] already exists 

Check integrations / kubernetes / kubernetes: check / system test: default – kubernetes.state_container

• no error details
Expand to view the stacktrace

 one or more errors found in documents stored in metrics-kubernetes.state_container-ep data stream: [0] found error.message in event: field [kubernetes.namespace.name] already exists 

Steps errors

Expand to view the steps failures

Test integration: kubernetes

• Took 37 min 34 sec . View more details here
• Description: eval "$(../../build/elastic-package stack shellinit)" ../../build/elastic-package test -v --report-format xUnit --report-output file --test-coverage

🤖 GitHub comments

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

• /test : Re-trigger the build.

[ChrsMark]

@marcin I think it is expected to fail if it runs against 8.0 and without the changes of #2041. Chicken-egg problem here :)

[mtojek]

Ok then, @ChrsMark :) Do you think I can merge it now and resolve these problems with your PR?

[ChrsMark]

Yeap its controllermanager-ep and scheduler-ep that failing! Ship it!