Add OIDC authentication for Spark History Server

Open
  • Is something wrong?
#806 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
kubernetes, rust
Domain
authentication, backend

Research direction

The issue names no files, tests, or entry points. Start by reading how the operator configures the Spark History Server and how it handles AuthenticationClass for other components. Define the OIDC integration scope and acceptance criteria with maintainers; done means the History Server supports AuthenticationClass-based authentication.

Written by the indexing model from the issue text.

Description

Right now, the history server comes without any authentication - adding an AuthenticationClass would allow us to later on e.g. filter applications based on user information and so on.

Dominant language
Rust
Stars
74
Forks
6
Avg merge
1d 1h
Merged PRs (30d)
15

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

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/spark-k8s-operator

All issues in stackabletech/spark-k8s-operator

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.