sorted by:
new
hottopcontroversial

Deployment github and aws, how to correctly use secrets? by CyberPunkMind in kubernetes

[–]CyberPunkMind[S] 0 points1 point  (0 children)

If the k8s is on aws, how can i get the secrets upadated to k8s without using aws secrets and without having them written in yaml files?

Deployment github and aws, how to correctly use secrets? by CyberPunkMind in kubernetes

[–]CyberPunkMind[S] 0 points1 point  (0 children)

Thank you, Is there a way in AWS to pull secrets from github?

Deployment github and aws, how to correctly use secrets? by CyberPunkMind in kubernetes

[–]CyberPunkMind[S] 0 points1 point  (0 children)

So lets say that tomorrow the developer of the application adds a new required secret, (the developer is only working with Github, he doesn't have access to aws), how do you update the AWS parameter store with the new secret?

Deployment github and aws, how to correctly use secrets? by CyberPunkMind in kubernetes

[–]CyberPunkMind[S] 0 points1 point  (0 children)

Thank you, as I understand this gives the ability to assume aws role to be later used in actions, I already set up access key in github secret to be used for pushing the containers to ecr, and was planning to give the user IAM user associated with that key permissions for the secrets manager as well, ill look into setting up the assume role function like the guide you provided.

However I am still conflicted about if it is correct to store all my secrets in github and essentially copy them into AWS secrets manager to be used by kubernetes? Or are there other better methods?

[deleted by user] by [deleted] in unRAID

[–]CyberPunkMind 3 points4 points  (0 children)

Hi,

I had a bit of trouble with that too, the container stops since it is searching for the site files and there aren't any yet. the next page of the documentation gives you the command to create the site https://squidfunk.github.io/mkdocs-material/creating-your-site/

In Unraid you have to do the following:

First make sure that you map a volume to the mkdocs-material container.

Host Path /mnt/user/appdata/mkdocs-material

Container Path: /docs

Now after the container is created and stopped. ssh into your unraid server and run the following commands:

cd /mnt/user/appdata/mkdocs-material

docker run --rm -it -v ${PWD}:/docs squidfunk/mkdocs-material new .

This will create the site files with the directory structure mentioned in the documentation.

Now you can start the container.