Skip to content
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

Add an all-in-one chart that deploys both the operator and an agent #91

Merged
merged 2 commits into from
May 26, 2020

Conversation

L3n41c
Copy link
Member

@L3n41c L3n41c commented May 20, 2020

What does this PR do?

Add an all-in-one chart that deploys both the operator and an agent

Motivation

Simplify on-boarding

Additional Notes

Anything else we should know when reviewing?

@codecov-commenter
Copy link

codecov-commenter commented May 20, 2020

Codecov Report

Merging #91 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master      #91   +/-   ##
=======================================
  Coverage   57.19%   57.19%           
=======================================
  Files          31       31           
  Lines        4175     4175           
=======================================
  Hits         2388     2388           
  Misses       1606     1606           
  Partials      181      181           
Flag Coverage Δ
#unittests 57.19% <ø> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4cb9aaf...ef836e0. Read the comment docs.

@@ -24,140 +28,36 @@ To use the Datadog Operator, deploy it in your Kubernetes cluster. Then create a
4. Create the namespace:

```shell
kubectl create ns $DD_NAMESPACE
kubectl create namespace $DD_NAMESPACE

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@L3n41c could we remove step 3 and 4 and use the default namespace and a default deployment name? it would simplify the basic deployment even further

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @cohenyair !
Thanks you for the feedback.
I’ve simplified the instructions by letting the agent being installed in the current namespace.
Can you PTAL ?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's great! LGTM

@L3n41c L3n41c marked this pull request as ready for review May 25, 2020 12:53
@L3n41c L3n41c requested review from a team as code owners May 25, 2020 12:53
@L3n41c L3n41c requested a review from cohenyair May 25, 2020 13:35
Copy link
Contributor

@apigirl apigirl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

small feedback

docs/getting_started.md Show resolved Hide resolved
@clamoriniere clamoriniere merged commit 6527795 into master May 26, 2020
@clamoriniere clamoriniere deleted the lenaic/chart_all-in-one branch May 26, 2020 20:19
@clamoriniere clamoriniere added this to the v0.3 milestone Jun 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants