Is your feature request related to a problem? Please describe.
Access to the Kubernetes cluster is by default enabled for any workshop session. Historically this was because training environments were mainly to teach users about Kubernetes. It was only afterwards that an option was added to disable access. This means it isn't as secure as possible by default.
Describe the solution you'd like
Due to backward compatibility with existing workshops, hard to make the default be no access in the underlying platform, so for now add configuration to the workshop definition created by educates new-workshop to disable it explicitly. Thus for anyone creating new workshops using the template they would need to enable it explicitly or remove the options so uses underlying default of being enabled.
Is your feature request related to a problem? Please describe.
Access to the Kubernetes cluster is by default enabled for any workshop session. Historically this was because training environments were mainly to teach users about Kubernetes. It was only afterwards that an option was added to disable access. This means it isn't as secure as possible by default.
Describe the solution you'd like
Due to backward compatibility with existing workshops, hard to make the default be no access in the underlying platform, so for now add configuration to the workshop definition created by
educates new-workshopto disable it explicitly. Thus for anyone creating new workshops using the template they would need to enable it explicitly or remove the options so uses underlying default of being enabled.Thus include in workshop template:
Describe alternatives you've considered
No response
Additional information
No response