Skip to content

chore: Remove minio addon - #378

Merged
HomayoonAlimohammadi merged 1 commit into
mainfrom
chore/remove-minio
Dec 17, 2025
Merged

chore: Remove minio addon#378
HomayoonAlimohammadi merged 1 commit into
mainfrom
chore/remove-minio

Conversation

@HomayoonAlimohammadi

Copy link
Copy Markdown
Contributor

Overview

This PR removes minio addon since it's entered maintenance mode.

@HomayoonAlimohammadi
HomayoonAlimohammadi marked this pull request as ready for review December 15, 2025 15:36

@berkayoz berkayoz left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should turn the enable command into a no-op / deprecation(removal) warning and keep the disable script as is. We should let users disable the addon. We can drop testing for it as well.

@HomayoonAlimohammadi

Copy link
Copy Markdown
Contributor Author

Great point, thanks for the review @berkayoz! I've added a deprecation note to the enable script and addon description as well.

Signed-off-by: Homayoon (Hue) Alimohammadi <homayoon.alimohammadi@canonical.com>

@berkayoz berkayoz left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, have you tested the disabling under deprecation?

@HomayoonAlimohammadi

HomayoonAlimohammadi commented Dec 17, 2025

Copy link
Copy Markdown
Contributor Author

@berkayoz yes, here's the result:

# starting from a microk8s that still has the minio addon intact
$ root@microk8s:~# microk8s enable minio
Infer repository core for addon minio
Infer repository core for addon dns
Addon core/dns is already enabled
Infer repository core for addon helm3
Addon core/helm3 is already enabled
Infer repository core for addon hostpath-storage
Enabling default storage class.
WARNING: Hostpath storage is not suitable for production environments.
         A hostpath volume can grow beyond the size limit set in the volume claim manifest.

deployment.apps/hostpath-provisioner created
storageclass.storage.k8s.io/microk8s-hostpath created
serviceaccount/microk8s-hostpath created
clusterrole.rbac.authorization.k8s.io/microk8s-hostpath created
clusterrolebinding.rbac.authorization.k8s.io/microk8s-hostpath created
Storage will be available soon.
Installing minio operator
Release "minio-operator" does not exist. Installing it now.
NAME: minio-operator
LAST DEPLOYED: Wed Dec 17 08:54:34 2025
NAMESPACE: minio-operator
STATUS: deployed
REVISION: 1
TEST SUITE: None
Create default tenant with:

  Name: microk8s
  Capacity: 20Gi
  Servers: 1
  Volumes: 1
  Storage class: microk8s-hostpath
  TLS: no
  Prometheus: no

secret/microk8s-user-1 created
++ tr -dc A-Za-z0-9
++ head -c 20
++ tr -dc A-Za-z0-9
++ head -c 40
+ /snap/microk8s/x1/microk8s-helm3.wrapper upgrade --install microk8s tenant --repo https://operator.min.io --version v7.1.1 --namespace minio-operator --set tenant.name=microk8s --set 'tenant.users[0].name=microk8s-user-1' --set 'tenant.pools[0].name=microk8s' --set 'tenant.pools[0].storageClassName=microk8s-hostpath' --set 'tenant.pools[0].size=20Gi' --set 'tenant.pools[0].servers=1' --set 'tenant.pools[0].volumesPerServer=1' --set tenant.configuration.name=microk8s-env-configuration --set tenant.configSecret.name=microk8s-env-configuration --set tenant.configSecret.accessKey=g8vvgpH6tWvkqXG1HQ5H --set tenant.configSecret.secretKey=fjRsyayjb78zFTCMs8qrFnGgbgoILatNh9cCTpyk --set secrets= --set tenant.certificate.requestAutoCert=false
Release "microk8s" does not exist. Installing it now.
NAME: microk8s
LAST DEPLOYED: Wed Dec 17 08:54:35 2025
NAMESPACE: minio-operator
STATUS: deployed
REVISION: 1
TEST SUITE: None
+ set +x
================================
Enabled minio addon.

You can interact with minio through the minio client (https://min.io/docs/minio/linux/reference/minio-mc.html#minio-client).

$ root@microk8s:~# cd core-addons/

$ root@microk8s:~/core-addons# git status
On branch chore/remove-minio
nothing to commit, working tree clean


$ root@microk8s:~# microk8s addons repo remove core
Removing /var/snap/microk8s/common/addons/core

$ root@microk8s:~# cp -r core-addons/ /var/snap/microk8s/common/addons/core/

$ root@microk8s:~# microk8s enable minio
Infer repository core for addon minio
Addon core/minio is already enabled

$ root@microk8s:~# microk8s disable minio
Infer repository core for addon minio
+ echo 'Cleaning up MinIO tenants and operator'
Cleaning up MinIO tenants and operator
+ HELM=/snap/microk8s/x1/microk8s-helm3.wrapper
+ KUBECTL=/snap/microk8s/x1/microk8s-kubectl.wrapper
+ NAMESPACE=minio-operator
++ /snap/microk8s/x1/microk8s-helm3.wrapper list -n minio-operator --short
++ grep -v minio-operator
+ tenant_name=microk8s
+ /snap/microk8s/x1/microk8s-kubectl.wrapper delete -n minio-operator secret microk8s-user-1
secret "microk8s-user-1" deleted from minio-operator namespace
+ /snap/microk8s/x1/microk8s-helm3.wrapper list -n minio-operator --short
+ xargs /snap/microk8s/x1/microk8s-helm3.wrapper uninstall -n minio-operator
release "microk8s" uninstalled
release "minio-operator" uninstalled
+ echo 'Disabled minio addon.'
Disabled minio addon.

$ root@microk8s:~# microk8s enable minio
Infer repository core for addon minio
The Minio addon is deprecated and cannot be enabled. It will be completely removed in the upcoming versions.
You can run 'microk8s disable minio' to remove the minio-operator from your cluster.

$ root@microk8s:~# k get all -A |grep minio
@HomayoonAlimohammadi
HomayoonAlimohammadi merged commit 941c778 into main Dec 17, 2025
4 checks passed
@HomayoonAlimohammadi
HomayoonAlimohammadi deleted the chore/remove-minio branch December 17, 2025 08:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants