Re: [PR] [helm] Add extraVolumes, extraVolumeMounts, initContainers [fluss]

2026-04-09 Thread via GitHub


polyzos merged PR #3034:
URL: https://github.com/apache/fluss/pull/3034


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [PR] [helm] Add extraVolumes, extraVolumeMounts, initContainers [fluss]

2026-04-09 Thread via GitHub


morazow commented on PR #3034:
URL: https://github.com/apache/fluss/pull/3034#issuecomment-4213259230

   Again somehow I cannot resolve my comments 🤔 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [PR] [helm] Add extraVolumes, extraVolumeMounts, initContainers [fluss]

2026-04-09 Thread via GitHub


affo commented on code in PR #3034:
URL: https://github.com/apache/fluss/pull/3034#discussion_r3056643789


##
website/docs/install-deploy/deploying-with-helm.md:
##
@@ -434,6 +444,44 @@ configurationOverrides:
   remote.data.dir: "s3://my-bucket/fluss-data"
 ```
 
+### Loading Filesystem Plugins via Init Containers
+
+Fluss discovers filesystem plugins at startup by scanning subdirectories under 
`$FLUSS_HOME/plugins/`.  
+To load a plugin that is not bundled in the base image, you can use an init 
container to download the plugin jar
+into a shared `emptyDir` volume before the main container starts.
+
+The example below loads the Azure filesystem plugin (`fluss-fs-azure`)
+so that Fluss can read and write remote data to Azure Blob Storage
+(replace `$FLUSS_VERSION$` with the version of Fluss you are deploying, e.g., 
`1.0`):
+
+```yaml
+_fsAzurePlugin: &fsAzurePlugin
+  extraVolumes:
+- name: azure-plugin
+  emptyDir: {}
+  extraVolumeMounts:
+- name: azure-plugin
+  mountPath: /opt/fluss/plugins/azure
+  initContainers:
+- name: download-fs-azure
+  image: alpine:3.20
+  command:
+- sh
+- -c
+- |
+  wget -O /plugins/azure/fluss-fs-azure-$FLUSS_VERSION$.jar \
+
https://downloads.apache.org/incubator/fluss/$FLUSS_VERSION$/fluss-fs-azure-$FLUSS_VERSION$.jar

Review Comment:
   addressed



##
website/docs/install-deploy/deploying-with-helm.md:
##
@@ -434,6 +444,44 @@ configurationOverrides:
   remote.data.dir: "s3://my-bucket/fluss-data"
 ```
 
+### Loading Filesystem Plugins via Init Containers
+
+Fluss discovers filesystem plugins at startup by scanning subdirectories under 
`$FLUSS_HOME/plugins/`.  
+To load a plugin that is not bundled in the base image, you can use an init 
container to download the plugin jar
+into a shared `emptyDir` volume before the main container starts.
+
+The example below loads the Azure filesystem plugin (`fluss-fs-azure`)
+so that Fluss can read and write remote data to Azure Blob Storage
+(replace `$FLUSS_VERSION$` with the version of Fluss you are deploying, e.g., 
`1.0`):
+
+```yaml
+_fsAzurePlugin: &fsAzurePlugin
+  extraVolumes:
+- name: azure-plugin
+  emptyDir: {}
+  extraVolumeMounts:
+- name: azure-plugin
+  mountPath: /opt/fluss/plugins/azure
+  initContainers:
+- name: download-fs-azure
+  image: alpine:3.20
+  command:
+- sh
+- -c
+- |
+  wget -O /plugins/azure/fluss-fs-azure-$FLUSS_VERSION$.jar \

Review Comment:
   addressed



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [PR] [helm] Add extraVolumes, extraVolumeMounts, initContainers [fluss]

2026-04-09 Thread via GitHub


morazow commented on code in PR #3034:
URL: https://github.com/apache/fluss/pull/3034#discussion_r3056348366


##
website/docs/install-deploy/deploying-with-helm.md:
##
@@ -434,6 +444,44 @@ configurationOverrides:
   remote.data.dir: "s3://my-bucket/fluss-data"
 ```
 
+### Loading Filesystem Plugins via Init Containers
+
+Fluss discovers filesystem plugins at startup by scanning subdirectories under 
`$FLUSS_HOME/plugins/`.  
+To load a plugin that is not bundled in the base image, you can use an init 
container to download the plugin jar
+into a shared `emptyDir` volume before the main container starts.
+
+The example below loads the Azure filesystem plugin (`fluss-fs-azure`)
+so that Fluss can read and write remote data to Azure Blob Storage
+(replace `$FLUSS_VERSION$` with the version of Fluss you are deploying, e.g., 
`1.0`):
+
+```yaml
+_fsAzurePlugin: &fsAzurePlugin
+  extraVolumes:
+- name: azure-plugin
+  emptyDir: {}
+  extraVolumeMounts:
+- name: azure-plugin
+  mountPath: /opt/fluss/plugins/azure
+  initContainers:
+- name: download-fs-azure
+  image: alpine:3.20
+  command:
+- sh
+- -c
+- |
+  wget -O /plugins/azure/fluss-fs-azure-$FLUSS_VERSION$.jar \
+
https://downloads.apache.org/incubator/fluss/$FLUSS_VERSION$/fluss-fs-azure-$FLUSS_VERSION$.jar

Review Comment:
   Should we change this to mvn central links? Apparently downloads don't have 
filesystem plugins.
   
   Maven link: 
https://repo1.maven.org/maven2/org/apache/fluss/fluss-fs-azure/0.9.0-incubating/
   



##
website/docs/install-deploy/deploying-with-helm.md:
##
@@ -434,6 +444,44 @@ configurationOverrides:
   remote.data.dir: "s3://my-bucket/fluss-data"
 ```
 
+### Loading Filesystem Plugins via Init Containers
+
+Fluss discovers filesystem plugins at startup by scanning subdirectories under 
`$FLUSS_HOME/plugins/`.  
+To load a plugin that is not bundled in the base image, you can use an init 
container to download the plugin jar
+into a shared `emptyDir` volume before the main container starts.
+
+The example below loads the Azure filesystem plugin (`fluss-fs-azure`)
+so that Fluss can read and write remote data to Azure Blob Storage
+(replace `$FLUSS_VERSION$` with the version of Fluss you are deploying, e.g., 
`1.0`):
+
+```yaml
+_fsAzurePlugin: &fsAzurePlugin
+  extraVolumes:
+- name: azure-plugin
+  emptyDir: {}
+  extraVolumeMounts:
+- name: azure-plugin
+  mountPath: /opt/fluss/plugins/azure
+  initContainers:
+- name: download-fs-azure
+  image: alpine:3.20
+  command:
+- sh
+- -c
+- |
+  wget -O /plugins/azure/fluss-fs-azure-$FLUSS_VERSION$.jar \

Review Comment:
   I wonder if the `$FLUSS_VERSION$` is going to render on the documentation 
site 🤔 



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]