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

chore(*) update ecs examples #1446

Merged
merged 7 commits into from
Jan 20, 2021
Merged

chore(*) update ecs examples #1446

merged 7 commits into from
Jan 20, 2021

Conversation

nickolaev
Copy link
Contributor

Summary

Update the ECS examples to reflect the latest developments

Documentation

@nickolaev nickolaev requested a review from a team as a code owner January 19, 2021 15:23
@nickolaev nickolaev changed the title Chore/update ecs example chore(*) update ecs examples Jan 19, 2021
@@ -280,6 +345,9 @@ Resources:
Essential: true
User: '5678'
Environment:
- Name: KUMA_DATAPLANE_RUNTIME_TOKEN
# generated with "wget --header='Content-Type: application/json' --post-data='{\"mesh\": \"default\", \"type\": \"ingress\"}' -qO- http://localhost:5681/tokens"
Value: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJOYW1lIjoiIiwiTWVzaCI6ImRlZmF1bHQiLCJUYWdzIjp7fSwiVHlwZSI6ImluZ3Jlc3MifQ.62MCnX4pCJztiLsqDSOopKxCDbxGstFrGZ1jboPOcoA
Copy link
Contributor

Choose a reason for hiding this comment

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

How does it work? The signing key for dataplane token is changing with every restart if you don't use persistent storage.

Should we instruct the users to replace it with the value generated after deploying global CP and generating the token?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Oh that now makes much more sense, maybe I should split the ingress to a separate template and instruct to actually generate the token as with the regular workload.

Copy link
Contributor

Choose a reason for hiding this comment

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

I think that makes sense

@nickolaev nickolaev force-pushed the chore/update_ecs_example branch from e9e5ff3 to 07e0c15 Compare January 20, 2021 13:55
@nickolaev nickolaev merged commit 0362bca into master Jan 20, 2021
@nickolaev nickolaev deleted the chore/update_ecs_example branch January 20, 2021 13:57
mergify bot pushed a commit that referenced this pull request Jan 20, 2021
* fix(*) bootstrap pem decode error check

* chore(*) bump default version to 1.0.5

* chore(*) make basic standalone work

* chore(*) make multizone work

* docs(*) update README

* chore(*) split ingress to a separate template

Signed-off-by: Nikolay Nikolaev <[email protected]>
(cherry picked from commit 0362bca)
nickolaev pushed a commit that referenced this pull request Jan 20, 2021
* fix(*) bootstrap pem decode error check

* chore(*) bump default version to 1.0.5

* chore(*) make basic standalone work

* chore(*) make multizone work

* docs(*) update README

* chore(*) split ingress to a separate template

Signed-off-by: Nikolay Nikolaev <[email protected]>
(cherry picked from commit 0362bca)

Co-authored-by: Nikolay Nikolaev <[email protected]>
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.

2 participants