You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In addons for canonical-kubernetes, spell we install via helm. If a "default" persistent storage class is created during cluster creation before addons are executed, pv claims can be accomodated and aws ebs volumes can get created.
How would this help? - The addon script will be much simpler and fewer kubectl statements. The idea is to create resources only via helm and only use kubectl for exceptions. With a standard default storageclass, all helm installs can refer to this storageclass,
The text was updated successfully, but these errors were encountered:
In addons for canonical-kubernetes, spell we install via helm. If a "default" persistent storage class is created during cluster creation before addons are executed, pv claims can be accomodated and aws ebs volumes can get created.
How would this help? - The addon script will be much simpler and fewer kubectl statements. The idea is to create resources only via helm and only use kubectl for exceptions. With a standard default storageclass, all helm installs can refer to this storageclass,
The text was updated successfully, but these errors were encountered: