Kamil Krzywicki
Kamil Krzywicki
In order to fulfill restricted PodSecurity policy requirements, helm chart should add as a default on the pod or container level: ``` seccompProfile: type: "RuntimeDefault" ```
**Is your feature request related to a problem? Please describe.** It would be usefull to create API tokens with this terraform provider **Describe the solution you'd like** Resource like: `virtual_environment_api_token`...
1. I created a themes.json file: ``` { "themes": [ { "label": "Dark", "value": 0, "mainColor": "#ffffff", "accentColor": "#999999", "backgroundColor": "#000000" }, { "label": "Lime", "value": 8, "mainColor": "#aabbc3", "accentColor":...
Resolves #8 I implemented helm chart for synology-csi deployment. It uses github as helm chart registry, but requires setup of github pages as described in https://helm.sh/docs/howto/chart_releaser_action/
Currently there is no option to trigger talos upgrade through terraform provider. If I aplly new kubernetes version through talos resources all nodes get patched simultaneously. It would be great...
1. go to https://www.civo.com/account/volumes 2. click "Create volume" 3. Screen is covered with gray layer and there is only "Loading ..." (Browser Opera 69.0.3686.36 @ Linux MInt 19.3)
1. create k3s cluster (3 nodes, medium) 2. add firewall rule: `civo firewall rule create FIREWALL_ID -c 'MY_PUBLIC_IP/32' -d ingress -s 6443 -e 6443 -p TCP -l k8s` 3. remove...
Please search the existing issues for relevant feature requests, and use the reaction feature (https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to add upvotes to pre-existing requests. #### Community Note Please vote on this issue by...
I tried to provide my ssh key (ed25519) as encryption key but got error: ``` key: malformed recipient "ssh-ed25519 AAAxxxxxx": mixed case ```
It would be great if encryption of backup could be optional and can be switched off. Usually cloud provider's have their own mechanisms to encrypt data in S3 compatible storage.