helm-charts
Here are 855 public repositories matching this topic...
-
Updated
Jan 5, 2022 - Mustache
Description of the problem/feature request
Add a configuration (flag, env var, …) to force the colored output
Description of the existing behavior vs. expected behavior
When not run from a terminal, there is no color in the output. This is usually fine, except in a few cases, like during continuous integration.
Additional context
I'm running kube-linter from gitlab-ci, and wou
-
Updated
Dec 23, 2020 - Shell
JSON schema
Please, provide json schema with comments(docs), instead of desired state specification and some particular tom/yaml cases, for standardized IDE support/documentation.
VScode , for example, can use - Even Better TOML
-
Updated
Sep 5, 2020 - Jupyter Notebook
Please create ingress template and configuration for:
- kafka-rest
- kafka-connect
- schema-registry
-
Updated
Nov 24, 2021
-
Updated
Jan 5, 2022 - Smarty
-
Updated
Jan 5, 2022 - Go
-
Updated
Dec 28, 2021 - Shell
Test cases are failing for status pages which reflect that there is some API change from the service providers. We should update our implementation for handling status pages and fix those test cases.
-
Updated
Jan 1, 2018 - Go
-
Updated
Feb 22, 2021 - Shell
-
Updated
Jan 3, 2022 - Go
See jenkinsci/jenkins#5899 (comment)
Set -Dhudson.lifecycle=hudson.lifecycle.ExitLifecycle in the system properties so that restarts from Jenkins don't try and restart in the same process, it instead lets Kubernetes restart it.
-
Updated
Dec 16, 2021 - Go
-
Updated
Dec 29, 2021 - Makefile
-
Updated
Dec 24, 2021 - Smarty
-
Updated
Jan 3, 2022 - Smarty
-
Updated
Aug 6, 2021 - Makefile
I came across a helm chart that generated manifests such as the following:
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1beta1
Because the mapping file is using a multiline substring match that looks for apiVersion followed by kind, the tool did not recognize these resources as needing to be updated. I had to manually edit the map file to switch the order to get it
-
Updated
Jun 2, 2020 - TypeScript
-
Updated
Jan 5, 2022 - HCL
The upstream issues got closed. It is referenced in:
- helm/charts/hydra-maester/values.yaml#L66
- [helm/charts/keto/values.yaml#L34](https://github.com/ory/k8s/blob/47329d4a0f0295b7c745d849e51a6867bc25b05e/helm/chart
-
Updated
Apr 1, 2021
-
Updated
Jan 4, 2022 - Shell
-
Updated
Sep 23, 2021 - Go
Improve this page
Add a description, image, and links to the helm-charts topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the helm-charts topic, visit your repo's landing page and select "manage topics."
CKV_AWS_116 flags any Lambda without a dead-letter queue (DLQ) enabled. There's no explanation given for this recommendation:
https://docs.bridgecrew.io/docs/ensure-that-aws-lambda-function-is-configured-for-a-dead-letter-queue-dlq
AWS has retired it from their Foundational Security Best Practices controls on August 31, 2021:
https://docs.aws.amazon.com/securityhub/latest/userguide/securi