Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

support terminated_https on load balancer clouddriver #1098

Closed
derekolk opened this issue Sep 1, 2016 · 6 comments
Closed

support terminated_https on load balancer clouddriver #1098

derekolk opened this issue Sep 1, 2016 · 6 comments

Comments

@derekolk
Copy link

derekolk commented Sep 1, 2016

Provide a caching endpoint for certs that will allow users to select an available cert.
Modify existing upsert atomic operation to take in selected cert.

@derekolk
Copy link
Author

derekolk commented Sep 6, 2016

Scenario:

  • Allow user to pass in TLS container name and optionally list of SNI container names when the external protocol TERMINATED_HTTPS is selected.

Design:

  • Validate container names passed and throw client exception (4XX) if invalid
  • Pass HATEOS references into openstack listener creation.

Impact:

  • UpsertOpenstackLoadBalancerAtomicOperation
  • Requires changes to openstack4j for Barbican

Reference

Blocker

@derekolk
Copy link
Author

The only way that I have been able to get this working is to create a container and load balancer in the admin project. Not able associate a container to a load balancer in non-admin project. Trying to reach out to openstack team to see if there is a work around for this.

@derekolk
Copy link
Author

derekolk commented Sep 16, 2016

Have a blocker when creating/updating listener with sniContainerRefs ... https://bugs.launchpad.net/octavia/+bug/1624512

@spinnakerbot
Copy link

This issue is tagged as 'stale' and hasn't been updated in 89 days, so we are tagging it as 'to-be-closed'. It will be closed in 45 days unless updates are made. If you want to remove this label, comment:

@spinnakerbot remove-label to-be-closed

@spinnakerbot
Copy link

This issue is tagged as 'to-be-closed' and hasn't been updated in 45 days, so we are closing it. You can always reopen this issue if needed.

1 similar comment
@spinnakerbot
Copy link

This issue is tagged as 'to-be-closed' and hasn't been updated in 45 days, so we are closing it. You can always reopen this issue if needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants