k3s, csi-smb: Ports and Values about charts HOT 9 CLOSED

How about getting rid of 90% of that values.yaml file?
Half of it is either wrong or not needed.

Things like this are advanced, completely unneeded, and not well tested at all:

    global:
      namespace: csi-smb

from charts.

This is either not a thing anymore or the settings are wrong:

    manifestManager:
      enabled: false
    operator:
      register: true

from charts.

    service:
      main:
        enabled: false
        ports:
          main:
            enabled: true
    workload:

This makes no sense.

from charts.

TLDR:

Stop altering value that don't need to be altered.
ONLY modify if something explicitly needs modifications for your setup.

I'm closing this, as this issue is so full of usererror that we cannot spend devtime on this.
Please be aware that github issues are only for bugs, support is given through our dedicated support staff on Discord through out ticketing system

from charts.

I took the base for the values from here: https://github.com/truecharts/charts/blob/master/charts/system/csi-driver-smb/values.yaml

And the documentation for the common and global values while attempting to look up what exactly most of these do. There was, unfortunately, no hint or alike that some of them were straight up unused, deprecated or the like o.o Good to know!

Thanks for the infos though, much appreciated.

from charts.

Some more notes:

• k3s is not an officially supported platform by us, though the helm charts should work (with some caveats)
• We don't support other sources of traefik than our own
• Klipper is not 'shrunken metallb' is a totally different thing with its own host of problems

from charts.

I took the base for the values from here: https://github.com/truecharts/charts/blob/master/charts/system/csi-driver-smb/values.yaml

And the documentation for the common and global values while attempting to look up what exactly most of these do. There was, unfortunately, no hint or alike that some of them were straight up unused, deprecated or the like o.o Good to know!

Lets be more clear about that:
You should only modify something if it needs modifications for your setup.

What you've done is copy the complete values.yaml, which is not how you use helm charts.
Your personal value file should only contain your personal overrides

from charts.

Another interesting note:
helm.cattle.io/v1

Is also not a supported deployment method by us.
Only normal helm is, we don't know how this works if it has bugs etc.

from charts.

I will show you what a correct values.yaml looks like:

    TZ: Europe/Berlin

Thats it.

The common docs aren't a "lets go over them all and see if I need it" kind of docs.
first need to determine what you want the chart to do, then find settings that you need changed to get it to function how you want it.

Another important note:
So I disabled the service, for now.

You cannot "just" disable random features and expect things to work.
If things don't work as expected out of the box, you find out how to fix it or file a support ticket.

Things are interconnected, you cannot just say "nah nuke that one component" and then be surprised other components start crashing

With all that being said, I op you now understand better why this is user error needing support tickets and not bug-report material.

from charts.