Skip to content
#

helm

Here are 1,685 public repositories matching this topic...

stefankip
stefankip commented Nov 28, 2019

I had some issues and talked on the slack channel with @hickeyma.
In the end the problem was me, not understanding the helm chart name and the release name.

So I had the following situation:
I didn't know in the beginning that the release name had to be unique within a namespace. I used the helm chart name as component name (copy, content, seo, orders etc.) and the release name initial for

calebwoofenden
calebwoofenden commented Mar 31, 2020

Is your feature request related to a problem? Please describe.
The documentation for this chart specifies that you can give it a logLevel parameter that has a default value of 4. It's not immediately obvious to me what this number means or what other numbers I could give to this parameter.

Describe the solution you'd like
It would be nice to enumerate on the documentation what val

flux
alexpilotti
alexpilotti commented Jun 8, 2018

When deploying on clusters with mixed Linux and Windows nodes, it's necessary to put a nodeSelector constraint to ensure that only nodes with the matching OS type get chosen by the scheduler.

The following should be added in the deployment specs for all the Linux deployment templates.

nodeSelector:
  beta.kubernetes.io/os: linux

Similarly Windows packs will need:

`beta.kub

vjpie2002
vjpie2002 commented Apr 30, 2020

Summary

Add field/label "LIVE For:" to show how much time the Revision was LIVE. Currently when a user clicks on the "History and Rollback", it shows all past Revisions and when it was triggered and completed and also displays the amount of time for which that Revision was LIVE. But it does not mention what these timings/durations are for (as shown in the attached screenshot where it shows dur

k3sup
LukasGentele
LukasGentele commented Jan 13, 2020

Is your feature request related to a problem?
"DevSpace should use the current docker behavior for dockerignore:
Dockerfile + .dockerignore
Dockerfile + Dockerfile.dockerignore
Dockerfile.frontend + Dockerfile.frontend.dockerignore
"

Which solution do you suggest?
Delegating the dockerignore file search to Docker if possible, otherwise copying the behavior as best as possible

jonathansantilli
jonathansantilli commented Dec 3, 2018

At the Dockercon18, Workshop: Docker Application Package, I have asked if the command validate is executed before sharing or deploying the app.
Since there was not a clear answer about it, they encouraged me to open this issue/question.
I have checked the code and seems that is not called, maybe is called, but I could not find it.
In my opinion would be great to ensure the app is valid befo

trankchung
trankchung commented Feb 8, 2020

Is there a list of all the possible labels/annotations that keel uses? I went through all the documentation but didn’t any any place that list them all. Could you please have a section in the Guide that list all the labels/annotations?

Also, why are labels and annotations used interchangeably? It doesn’t matter if either is used? Examples in the Guide sometimes using labels and sometimes using

xbl
xbl commented Jul 30, 2018

环境:

  • Mac
  • vagrant 2.1.2
  • virtualBox: 5.2.16
  • Kubernetes 1.11.0

遇到了几个问题:

  1. 在系统自动挂起之后vm 的时间会不对,没有自动同步,导致 Prometheus 监控数据显示不出来,应该同步时间就可以,不过我没有,而是使用的 vagrant halt ,就导致了另一个问题。
  2. 执行 vagrant halt 按照【重启】 的操作后,之前配置的 Istio 相关所有东西都不见了,包括 istio-system namespace 。
  3. 按照[文档](
okteto
rberrelleza
rberrelleza commented Feb 28, 2020

Is your feature request related to a problem? Please describe.
When running okteto as part of a script (or in the remote-kubernetes plugin) having the ascii animations makes reading the logs harder.

Describe the solution you'd like
I'd like to have a --headless (or similarly named parameter) that disables the animations and just prints text messages.

an-excellent-choice
an-excellent-choice commented Jun 19, 2019

The regex test if [[ $yml =~ ^(.*/)?secrets(\.[^.]+)*\.yaml$ ]] does not match the helm secrets help text, at least on OSX.

secrets.dev.yaml functions properly; secrets-dev.yaml fails to decrypt; helm secrets implies it should: wrapper that decrypts secrets[.*].yaml

Improve this page

Add a description, image, and links to the helm topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the helm topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.