Comments (18)
from kas-installer.
Are you thinking a wrapper/convenience script or guidance to use
rhoas
?+1 .I know for a fact that this is a planned work in the CLI, @dimakis can you confirm? So, I think kas-installer needs to only do it after the CLI has support for it. In the meanwhile, the user can directly call the KFM endpoint. What do you think?
indeed, we do plan on adding a de-register
command to the CLI 👍
from kas-installer.
So, I think kas-installer needs to only do it after the CLI has support for it. In the meanwhile, the user can directly call the KFM endpoint. What do you think?
I don't mind scripting it in the short term. At a minimum, it will give me some hands-on experience with the new endpoint(s) and would be good to have in the uninstall.sh
process too. It might be good to have a version de-registration available outside of rhoas
anyway for the un-installation to avoid relying on an active session, etc.
from kas-installer.
I don't mind scripting it in the short term. At a minimum, it will give me some hands-on experience with the new endpoint(s) and would be good to have in the
uninstall.sh
process too. It might be good to have a version de-registration available outside ofrhoas
anyway for the un-installation to avoid relying on an active session, etc.
Okay. One thing the script will need to do as well is - remove the AddOns.
from kas-installer.
Is it expected that the bootstrap domain does not have the kas
prefix when CNAME registration is not used? I see in rhoas
that the apps
subdomain is removed from the cluster DNS, which means KFM does not replace it with kas
.
from kas-installer.
@MikeEdgar @dimakis here is an attempt for a fix redhat-developer/app-services-cli#1806 please have a look.
from kas-installer.
make sure that KFM is running in OCM mode and not standalone mode when enterprise feature is to be used
Do you envision a new flag that indicates whether the user intends to use enterprise features and the installer performs some basic validation and generates an empty CLUSTER_LIST
based on that?
Update SUPPORTED_INSTANCE_TYPES: https://github.com/bf2fc6cc711aee1a0c2a/kas-fleet-manager/blob/main/templates/service-template.yml#L160 for include supported billing models
kas-installer currently just uses the default from the template unless the user intentionally overrides this via a kas-fleet-manager-service-template-params
script. With the tag update, the default value includes all of the billing types so we may be covered on this out-of-the-box. Thoughts?
Being able to deregister an enterprise cluster
Are you thinking a wrapper/convenience script or guidance to use rhoas
?
from kas-installer.
make sure that KFM is running in OCM mode and not standalone mode when enterprise feature is to be used
Do you envision a new flag that indicates whether the user intends to use enterprise features and the installer performs some basic validation and generates an empty
CLUSTER_LIST
based on that?
I was thinking this as well. What do you think?
Update SUPPORTED_INSTANCE_TYPES: https://github.com/bf2fc6cc711aee1a0c2a/kas-fleet-manager/blob/main/templates/service-template.yml#L160 for include supported billing models
kas-installer currently just uses the default from the template unless the user intentionally overrides this via a
kas-fleet-manager-service-template-params
script. With the tag update, the default value includes all of the billing types so we may be covered on this out-of-the-box. Thoughts?
+1. So is a quick win. I hope no one overrides the default one in their kas-fleet-manager-service-template-params
script.
Being able to deregister an enterprise cluster
Are you thinking a wrapper/convenience script or guidance to use
rhoas
?
+1 .I know for a fact that this is a planned work in the CLI, @dimakis can you confirm? So, I think kas-installer needs to only do it after the CLI has support for it. In the meanwhile, the user can directly call the KFM endpoint. What do you think?
from kas-installer.
Being able to register the cluster with KFM. We can use the latest release of the rhoas CLI for this.
Based on my understanding of the CLI on the dedicated
branch, we may be blocked on this until a separate OCM API endpoint can be specified.
from kas-installer.
Being able to register the cluster with KFM. We can use the latest release of the rhoas CLI for this.
Based on my understanding of the CLI on the
dedicated
branch, we may be blocked on this until a separate OCM API endpoint can be specified.
@dimakis created an alpha release a few weeks ago. Maybe we can have another one with latest changes on redhat-developer/app-services-cli#1804. Any plans on that @dimakis ?
from kas-installer.
Being able to register the cluster with KFM. We can use the latest release of the rhoas CLI for this.
Based on my understanding of the CLI on the
dedicated
branch, we may be blocked on this until a separate OCM API endpoint can be specified.@dimakis created an alpha release a few weeks ago. Maybe we can have another one with latest changes on redhat-developer/app-services-cli#1804. Any plans on that @dimakis ?
I'm just waiting for someone to approve those changes. As soon as I do I'll release another alpha with the latest changes.
from kas-installer.
Very nice, I didn't see that PR. I'll at least try to run that locally until there is a release with those changes. Thanks for mentioning it @machi1990 !
from kas-installer.
Very nice, I didn't see that PR. I'll at least try to run that locally until there is a release with those changes. Thanks for mentioning it @machi1990 !
there's an alpha release now with the most up to date changes:
curl -o- https://raw.githubusercontent.com/redhat-developer/app-services-cli/main/scripts/install.sh | bash -s v0.52.2-alpha1
will grap and install it 👍
from kas-installer.
Is it expected that the bootstrap domain does not have the
kas
prefix when CNAME registration is not used? I see inrhoas
that theapps
subdomain is removed from the cluster DNS, which means KFM does not replace it withkas
.
Good catch, that's a bug. apps.
should be there for the cluster_dns
when CNAME registration is not used. /cc @dimakis
from kas-installer.
@MikeEdgar @dimakis I'll prepare a PR against RHOAS CLI and ping you on it.
from kas-installer.
Is it expected that the bootstrap domain does not have the
kas
prefix when CNAME registration is not used? I see inrhoas
that theapps
subdomain is removed from the cluster DNS, which means KFM does not replace it withkas
.Good catch, that's a bug.
apps.
should be there for thecluster_dns
when CNAME registration is not used. /cc @dimakis
So are there instances of the DNS where the ".apps." Is not in the DNS?
from kas-installer.
So are there instances of the DNS where the ".apps." Is not in the DNS?
The default ingress for OSD handles the apps
subdomain, but for MK there are additional subdomains created where apps
is replaced with kas
. The current KFM logic just swaps the subdomain (search/replace) so it's expected to be there in the cluster configuration.
from kas-installer.
Thanks @MikeEdgar
all the tasks in this are completed. I’ll close the issue
from kas-installer.
Related Issues (20)
- kas-fleetshard should be installed using a bundle HOT 5
- kas-fleet-manager pod failed on installation: CrashLoopBackOff HOT 3
- Kafka instance creation is always failing HOT 7
- Request: replicate keycloak and keycloak-postgresql pods in all AZ HOT 1
- enable us-east-2 region HOT 2
- Allow for multi cloud provider and multi region support HOT 7
- Allow the configuration of the quota management list
- Release 0.2.0 release notes HOT 2
- Use the exposed admin server url HOT 1
- MANAGEDKAFKA_ADMINSERVER_EDGE_TLS_ENABLED broken HOT 2
- metrics not available through fleet-manager endpoint HOT 2
- Add instructions on how to generate operators bundle HOT 8
- Allow to configure KFM in dynamic scaling mode
- Support podman in operators/generate-kas-fleetshard-olm-bundle.sh
- Fail to scale down the kas-fleet-manager deployment during install
- Cannot install Observatorium CRDs on K8s 1.22+
- Integrate new KFM Quota list changes
- PodSecurity warnings from fleetmanager when deploying to OpenShift 4.11.18 HOT 6
- deployment keycloak-postgresql gets stuck HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from kas-installer.