Skip to content

fix: remove legacy service account binding #697

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

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,7 @@ All notable changes to this project will be documented in this file.
- The defaults from the docker images itself will now apply, which will be different from 1000/0 going forward
- This is marked as breaking because tools and policies might exist, which require these fields to be set
- Use versioned common structs ([#684]).
- BREAKING: remove legacy service account binding for cluster role nodes ([#697]).

### Fixed

Expand All @@ -52,6 +53,7 @@ All notable changes to this project will be documented in this file.
[#693]: https://github.com/stackabletech/hdfs-operator/pull/693
[#695]: https://github.com/stackabletech/hdfs-operator/pull/695
[#696]: https://github.com/stackabletech/hdfs-operator/pull/696
[#697]: https://github.com/stackabletech/hdfs-operator/pull/697

## [25.3.0] - 2025-03-21

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -73,26 +73,12 @@ pub async fn reconcile(
}
})
.flat_map(|(meta, sa_name)| {
let mut result = vec![
Subject {
kind: "ServiceAccount".to_string(),
name: sa_name,
namespace: meta.namespace.clone(),
..Subject::default()
},
// This extra Serviceaccount is being written for legacy/compatibility purposes
// to ensure that running clusters don't lose access to anything during an upgrade
// of the Stackable operators, this code can be removed in later releases
// The value is hardcoded here, as we have removed access to the private fns that
// would have built it, since this is a known target though, and will be removed soon
// this should not be an issue.
Subject {
kind: "ServiceAccount".to_string(),
name: "hdfs-serviceaccount".to_string(),
namespace: meta.namespace.clone(),
..Subject::default()
},
];
let mut result = vec![Subject {
kind: "ServiceAccount".to_string(),
name: sa_name,
namespace: meta.namespace.clone(),
..Subject::default()
}];
// If a cluster is called hdfs this would result in the same subject
// being written twicex.
// Since we know this vec only contains two elements we can use dedup for
Expand Down