[merge this on Dec 10 morning CET] Openscapes event

[GeorgianaElena]

Closes #3430

• I didn't get a confirmation about changing the shared directory to readonly persistently on the hub, so I've assumed we should only do it for the duration of the event
• I've changed the node type from r5.xlarge to r5.4xlarge for the 14.8GB profile to have the 50 expected users on ~7 nodes, this means only 14% of the users will experiment longer startup times due to a new node coming up as opposed to 50% of them with the original node type
• I've left the 7.4GB profile on r5.xlarge, as this will mean the 50 expected users of the second event on ~13 nodes, which means ~26 users of the users will experiment longer startup time, which I believe is acceptable.

[github-actions]

Merging this PR will trigger the following deployment actions.

Support and Staging deployments

Cloud Provider	Cluster Name	Upgrade Support?	Reason for Support Redeploy	Upgrade Staging?	Reason for Staging Redeploy
aws	openscapes	No		Yes	Following helm chart values files were modified: common.values.yaml

Production deployments

Cloud Provider	Cluster Name	Hub Name	Reason for Redeploy
aws	openscapes	prod	Following helm chart values files were modified: prod.values.yaml, common.values.yaml

[yuvipanda]

I love that this requires no eksctl changes, only helm changes.

[GeorgianaElena]

I've missed merging this because I've miscalculated and thought Dec 10th was today, on a Monday, but it was yesterday :((((

The event has now passed, so closing this one 😞

[damianavila]

The event has now passed, so closing this one 😞

Don't worry too much about it @GeorgianaElena, if we did not receive any feedback from them, I presume everything went OK!
In addition, support on Sundays, IMHO, is not expected given our current staffing/capacity and current guidelines/understanding.

[yuvipanda]

I spent last evening with them at a happy hour and they had no complaints :) don’t worry @GeorgianaElena!