Notes from discussion about ingress authentication related to:

Options:

• Service-level authentication: configure non-default passwords
• Ingress authentication: use the nginx ingress controller built-in facility for basic authentication

Use cases:

• Private: Some services will be user-private (e.g., development environments). In this case, it is desirable to secure the service with the users current username/password
• Restricted: Some services will be shared (e.g., Clowder). In this case, the user will want to distribute a link to the service with one or more shared usernames/passwords
• Public: Some services will need to be publich (e.g., Chisel).