You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many CKF charms have the port configuration option, which is problematic because of the following:
The configuration option is not consistent, in some it refers to the http_port, in some others it refers to the metrics_port, and the description in the configuration file is not clearly defining this. For example in dex-auth:
port:
type: int
default: 5556
description: Listening port
In many cases, the configuration option won't have any effect on the workload itself, only on certain things the charm could be doing with it, like when the KubernetesServicePatch is used. For example, in dex-auth, if changed, the configuration option will just affect the behaviour of the KubernetesServicePatch, but not the workload service as it is not changing anything in the command of the pebble layer.
In some other cases, like pipelines, the port is hardcoded, making it impossible to change.
It may add complexity to the port configuration as there could be many options, for example a HTTP and a HTTP port.
The use of this configuration option is inconsistent, some charms will have it while some others won't.
Proposal
To eliminate the option to configure ports in all CKF charms and refactor the charm code to avoid using them, unless there is a compelling reason to keep them.
Context
Many CKF charms have the
port
configuration option, which is problematic because of the following:http_port
, in some others it refers to themetrics_port
, and the description in the configuration file is not clearly defining this. For example index-auth
:KubernetesServicePatch
is used. For example, index-auth
, if changed, the configuration option will just affect the behaviour of the KubernetesServicePatch, but not the workload service as it is not changing anything in thecommand
of the pebble layer.In some other cases, like pipelines, the port is hardcoded, making it impossible to change.
It may add complexity to the port configuration as there could be many options, for example a HTTP and a HTTP port.
The use of this configuration option is inconsistent, some charms will have it while some others won't.
Proposal
To eliminate the option to configure ports in all CKF charms and refactor the charm code to avoid using them, unless there is a compelling reason to keep them.
Related issues:
port
configuration option is not configuring Dex's command dex-auth-operator#210What needs to get done
port
config option from all CKF charmsself.config['port']
or similarDefinition of Done
The
port
is not configurable anymore for any of the CKF charms.The text was updated successfully, but these errors were encountered: