OpenShift Route backend

Open
#303 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
kubernetes
Domain
infrastructure, networking

Research direction

Read the OpenShift Route CRD documentation first, then locate the existing serviceType integrations and Listener address handling. Done means creating Route objects and using a Route status host only when its Admitted condition is true; no repository files or tests are named in the issue.

Written by the indexing model from the issue text.

Description

OpenShift provides the Route CRD, which allows OpenShift to automatically allocate public hostnames for services and provides load balancing and a convention for DNS configuration.

We could integrate by:

  1. Creating a serviceType that creates Route objects
  2. Setting the Listener's addresses to Route.status.ingress[].host, but only if ingress[].conditions[type=Admitted].status=True (to prevent impersonation attempts)
Dominant language
Python
Stars
9
Forks
2
Avg merge
1d 9h
Merged PRs (30d)
8

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stackabletech/listener-operator

All issues in stackabletech/listener-operator

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.