Skip to content
This repository was archived by the owner on Jan 11, 2021. It is now read-only.

Conversation

@marjamis
Copy link
Owner

@marjamis marjamis commented Jan 6, 2019

A generic k8s manifest has been added to allow the ecr_reverse_proxy to be used within a k8s cluster which will resolve #2.

@marjamis marjamis self-assigned this Jan 6, 2019
@marjamis
Copy link
Owner Author

marjamis commented Jan 6, 2019

To merge this it will also require:

  • The automated build of the image in docker hub to be fixed.
  • The app to be able to run without requiring TLS and instead use the Ingress controllers TLS. Create a mode where TLS isn't required #6
  • README.md updated with any changes, if required.
  • Tested with the above changes.

service.beta.kubernetes.io/aws-load-balancer-internal: "0.0.0.0/0"
namespace: kube-system
spec:
type: LoadBalancer
Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be purely a ClusterIP as this will be used via an Ingress Controller.

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also look into restricting outside access completely as this should really only need to be used internally to the cluster.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Create a k8s manifest

2 participants