spark-operator/1.2.5 package update

[octo-sts]

[github-actions]

Package spark-operator: Click to expand/collapse

Package spark-operator:
Modified: /usr/bin/spark-operator

Package sparkctl: Click to expand/collapse

Package sparkctl:
Modified: /usr/bin/sparkctl

Package spark-operator-oci-entrypoint: Click to expand/collapse

Package spark-operator-oci-entrypoint:
Unchanged

bincapz found differences: Click to expand/collapse

Changed: sparkctl/usr/bin/sparkctl

RISK	KEY	DESCRIPTION
-2/MEDIUM	net/bpf	bPF (Berkeley Packet Filter)
-2/MEDIUM	procfs/self/exe	gets executable associated to this process
-2/MEDIUM	ref/words/ddos	references DDoS: "DD0S"
+1/LOW	cloud/aws/metadata	references the AWS EC2 metadata token

Changed: spark-operator/usr/bin/spark-operator

RISK	KEY	DESCRIPTION
-2/MEDIUM	ref/words/ddos	references DDoS: "DD0S"
+1/LOW	cloud/aws/metadata	references the AWS EC2 metadata token
-1/LOW	ref/path/hidden	possible hidden file path: "/home/build/.cache"

[debasishbsws]

As the Kubernetes is already in 1.29.3 and it is replaced by a lower version in upstream.
can't use gobump Error: Failed to run update. Error: package k8s.io/kubernetes with version 'v1.26.2' is already at version v1.29.3

But if we use script to do this we will not notice when there is a version update happening upstream and we will be downgrading the module version here.

I think it should be allowed to downgrade the go module version using gobump with some special flag.

OR is there any way to use gobump for this use case?

[github-actions]

Package spark-operator: Click to expand/collapse

Package spark-operator:
Modified: /usr/bin/spark-operator

Package sparkctl: Click to expand/collapse

Package sparkctl:
Modified: /usr/bin/sparkctl

Package spark-operator-oci-entrypoint: Click to expand/collapse

Package spark-operator-oci-entrypoint:
Unchanged

bincapz found differences: Click to expand/collapse

Changed: sparkctl/usr/bin/sparkctl

RISK	KEY	DESCRIPTION
-2/MEDIUM	net/bpf	bPF (Berkeley Packet Filter)
-2/MEDIUM	procfs/self/exe	gets executable associated to this process
-2/MEDIUM	ref/words/ddos	references DDoS: "DD0S"
+1/LOW	cloud/aws/metadata	references the AWS EC2 metadata token

Changed: spark-operator/usr/bin/spark-operator

RISK	KEY	DESCRIPTION
-2/MEDIUM	ref/words/ddos	references DDoS: "DD0S"
+1/LOW	cloud/aws/metadata	references the AWS EC2 metadata token
-1/LOW	ref/path/hidden	possible hidden file path: "/home/build/.cache"

[hectorj2f]

You can add a note about the reason to add these changes here.

[octo-sts]

superseded by #16987