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

BRH-301: Extend hatchery to launch prismacloud containers #2061

Merged
merged 1 commit into from
Nov 1, 2022

Conversation

jawadqur
Copy link
Contributor

Jira Ticket: BRH-301

New Features

  • Add ability to launch prismacloud containers using hatchery for security purposes.

Deployment changes

  • Currently requires to manually update prisma api key in json format under this path in the adminvm
    • ~/Gen3Secrets/prisma/apikey.json
  • format has to be the following:
{
  "AccessKeyID": "XXXX",
  "SecretKey": "XXXX"
}

This PR extends kube-setup-hatchery to create a kubernetes secret with for prisma cloud credentials, and extending the hatchery deployment to look for this secret and use it, if it exists.

@jawadqur jawadqur merged commit 5c3ba19 into master Nov 1, 2022
@jawadqur jawadqur deleted the feat/fargate_prisma branch November 1, 2022 20:40
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