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

New ingress converter and haproxy types (part 2) #295

Merged
merged 8 commits into from
Mar 13, 2019

Conversation

jcmoraisjr
Copy link
Owner

@jcmoraisjr jcmoraisjr commented Jan 29, 2019

Missing pieces between parsing ingress resources and reload HAProxy instance.

  • Parse globals - HAProxy global and HAProxy defaults
  • Parse most of the frontend annotations
  • K8s bindings - mostly cache / lister implementation
  • Other services implementations like named port, external name, etc
  • ModSecurity template
  • Starting version of HAProxy template

Some missing pieces to the next part:

  • Parsing some most of the annotations
  • Dynamic reload
  • API docs
  • Other k8s service implementations: named port and external name
  • Some converters and haproxy unit tests
  • Some global implementations like DrainSupport and Nbproc

Related with #289

Implements #274

@jcmoraisjr jcmoraisjr added this to the v0.8 milestone Jan 29, 2019
Global config is both configurations of global section from haproxy config file - eg nbproc, nbthread, DH param config, and also default values for frontends and backends - eg timeouts.

Updater knows both sides - k8s objects or maps with configs from the user, and haproxy objects used to populate the templates.

Legacy controller code is always used via interface - the only coupling is from `pkg/controller` code.
@jcmoraisjr jcmoraisjr force-pushed the jm-v08-controller-2 branch from a2c24d9 to 411f604 Compare March 10, 2019 22:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant