Allow specification of runtime user

[antechrestos]

Purpose

Allow specification of runAsUserand runAsGroup. This is needy as some cluster (like openshift) may have security constraints that only accepts some range (on our openshift instance for instance it must be in the ranges 1002150000, 1002159999)

Goals

Add some parameters un values.yml files with default value to 802 (the previous static value) and reference it in deployment template files.

Approach

Add two parameters in values.yml. These two are kubernetes.security.runtimeUser and kubernetes.security.runtimeGroup. I willingly put these values under kubernetesas to my mind it is global to the cluster and has nothing to do with a specific business component (am, mi, gateway...)

User stories

None

Release note

Add two parameters: kubernetes.security.runtimeUser to specify the securityContext.runAsUser and kubernetes.security.runtimeGroupto specify the securityContext.runAsGroup

Documentation

“N/A”

Certification

“N/A” pure kubernetes runtime issue

Marketing

“N/A”

Automation tests

“N/A”

Security checks

• Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes
• Ran FindSecurityBugs plugin and verified report? no
• Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes

Samples

“N/A”

Related PRs

“N/A”

Migrations (if applicable)

“N/A”

Test environment

“N/A”

Learning

“N/A”

[CLAassistant]

All committers have signed the CLA.