The primary purpose of this pull request is to update the permission of the script file, /home/gridftp/globus-connect-personal.sh
.
Dockerfile states it, but 744 was not applied in the image file, leading to a container-starting error.
In globus-connect.yaml, the image tag is added as some nodes pulled the old image which does not have the script file.
In the README.ME, export
is added for the environment variables, ep and epkey.
The primary purpose of this pull request is to update the permission of the script file, /home/gridftp/globus-connect-personal.sh
.
Dockerfile states it, but 744 was not applied in the image file, leading to a container-starting error.
In globus-connect.yaml, the image tag is added as some nodes pulled the old image which does not have the script file.
In the README.ME, export
is added for the environment variables, ep and epkey.
Adds globus-connect-personal.sh and calls the script upon starting. If there is an existing config on the persistent storage it copies it to /home/gridftp and starts the endpoint. If not, then it sleeps for an hour giving the user time to login and configure an endpoint.
Updated README to address change in functionality as well as adding directions for accessing the persistent storage in Globus and accessing the data in another pod after a transfer.
@dimm Here is the merge request I had mentioned.
Adds globus-connect-personal.sh and calls the script upon starting. If there is an existing config on the persistent storage it copies it to /home/gridftp and starts the endpoint. If not, then it sleeps for an hour giving the user time to login and configure an endpoint.
Updated README to address change in functionality as well as adding directions for accessing the persistent storage in Globus and accessing the data in another pod after a transfer.
The output of the following line in README.md
kubectl create -f globus-connect-service.yaml -n YourNS
is
Error from server (Forbidden): error when creating "globus-connect-service.yaml": admission webhook "validation.gatekeeper.sh" denied the request: [block-node-port] User is not allowed to create service of type NodePort
This is due to L10 on globus-connect-service.yaml.
Please reopen if you still need this
I'd explore other options first. S3 should be fine for most cases.
That is correct, you can not create the NodePort services. If you need one, we can talk, but it involves opening up the firewall too.
The output of the following line in README.md
kubectl create -f globus-connect-service.yaml -n YourNS
is
Error from server (Forbidden): error when creating "globus-connect-service.yaml": admission webhook "validation.gatekeeper.sh" denied the request: [block-node-port] User is not allowed to create service of type NodePort
This is due to L10 on globus-connect-service.yaml.
Dima Mishin (b0b5b880) at 08 Feb 12:14
Merge branch 'kkrick-master-patch-58114' into 'master'
... and 1 more commit
Dima Mishin (7cd7a6e7) at 01 Sep 10:52
Update Dockerfile