-
Notifications
You must be signed in to change notification settings - Fork 12
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
update kfp-api's apiserver configuration #375
update kfp-api's apiserver configuration #375
Conversation
This: * removes deprecated `DBCONFIG_USER`, etc, environment variables (they have been replaced by variables of name `DBCONFIG_[driver]CONFIG_*`) * adds `OBJECTSTORECONFIG_HOST`, `_PORT`, and `_REGION`, which previously were required. Although currently they seem to be ignored due to kubeflow/pipelines#9689 - but in theory they'll matter again? Not sure exactly the scope of that issue.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @ca-scribner, this change actually makes sense. As we tested it, the OBJECTSTORECONFIG_HOST
and OBJECTSTORECONFIG_PORT
env variables will actually be used by the apiserver when initialising the minio client.
I just left a minor comment to update the comments in the charm code to reflect what is actually happening.
NOTE: the integration tests are flaky at the moment, no need to block this PR because of them. Everything should be fixed after we do a last pass before merging to main.
charms/kfp-api/src/charm.py
Outdated
# Configurations charmed-kubeflow adds to those of upstream | ||
"ARCHIVE_CONFIG_LOG_FILE_NAME": self.model.config["log-archive-filename"], | ||
"ARCHIVE_CONFIG_LOG_PATH_PREFIX": self.model.config["log-archive-prefix"], | ||
# OBJECTSTORECONFIG_HOST and _PORT currently have no effect due to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we change this comment to say that these variables will actually have an effect and that they will be used in the absence of other env variables like MINIO_SERVICE_SERVICE_HOST
and a missing key in the config.json
? (related to #367 last two comments)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @ca-scribner LGTM!
* update kfp-api's apiserver configuration This: * removes deprecated `DBCONFIG_USER`, etc, environment variables (they have been replaced by variables of name `DBCONFIG_[driver]CONFIG_*`) * adds `OBJECTSTORECONFIG_HOST`, `_PORT`, and `_REGION`, which previously were required. Although currently they seem to be ignored due to kubeflow/pipelines#9689 - but in theory they'll matter again? Not sure exactly the scope of that issue.
This PR:
DBCONFIG_USER
, etc, environment variables (they have been replaced by variables of nameDBCONFIG_[driver]CONFIG_*
)OBJECTSTORECONFIG_HOST
,_PORT
, and_REGION
, which previously were required. Although currently they seem to be ignored due to [feature] remove hard-coded configs in KFP V2 launcher kubeflow/pipelines#9689 - but in theory they'll matter again? Not sure exactly the scope of that issue.afaict, these are both helpful changes. The first doesn't actually affect anything, but removes unnecessary configs. The second should affect things, if not for kubeflow/pipelines#9689
May close #367