N
Navy Horse
A number of functionalities across the Harness product would benefit from key changes.
  • Ability to review / extend the default Harness behaviours (IACM for example to allow additional cli tooling for use on self hosted k8s infrastructure)
  • Stop reliance on the "home" folder for all operations - if the home user is not set correctly due to security restrictions and alternate users applied - this results in attempted root file system modification which renders the image useless
  • Provide and publicize non-root users outside of key ranges for all functionality (over the reserved user ids up to 1000 at a minimum)
A number of the Harness current offerings do not work for us on our Openshift clusters due to security restrictions particularly with SE lInux contexts