assisted-service | This repository provides a service that installs OpenShift | Cloud library
kandi X-RAY | assisted-service Summary
kandi X-RAY | assisted-service Summary
This repository provides a service that installs OpenShift. Its main benefits include a minimum amount of prerequisites from the user's infrastructure, as well as comprehensive pre-flight validations to ensure a successful installation. The service exposes either a REST API, or it can be deployed as an Operator where it exposes a Kubernetes-native API via Custom Resources. A UI is available that uses the REST API. The Assisted Service can currently install clusters with highly-available control planes (3 hosts and above) and can also install Single-Node OpenShift (SNO). Highly available clusters are configured to use OpenShift's baremetal platform (typically used in bare metal IPI deployments), while SNO uses none (typically used in UPI deployments).
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
- NewHostStateMachine creates a new host state machine
- HandlerAPI returns an http . Handler for the AssistedInstall API
- NewAssistedInstallAPI creates a new AssistedInstallAPI instance
- NewClusterStateMachine returns a new StateMachine
- NewMetricsManager returns a new MetricsManager .
- Reconcile implements the ClusterService interface .
- NewPoolHostStateMachine creates a new state machine
- newValidations returns a list of validators .
- populateInfraEnv migrates infra_env table
- copyClusterUserInfoToInfraEnv copies cluster user information to InfraEnv .
assisted-service Key Features
assisted-service Examples and Code Snippets
# Step by step
make deploy-olm
make deploy-prometheus
make deploy-grafana
# Or just all-in
make deploy-monitoring
# Step by step
make deploy-prometheus TARGET=oc-ingress APPLY_NAMESPACE=false
make deploy-grafana TARGET=oc-ingress APPLY_NAMESPACE=fa
skipper make deploy-all DEPLOY_MANIFEST_PATH=./assisted-installer.yaml
skipper make deploy-all DEPLOY_MANIFEST_TAG=master
skipper make deploy-all DEPLOY_TAG=
skipper make deploy-all TARGET=oc-ingress
skipper make deploy-all TARGET=oc-ingress APPLY_NAMESPACE=False INGRESS_DOMAIN=apps.ocp.prod.psi.redhat.com
Community Discussions
Trending Discussions on assisted-service
QUESTION
I've got a problem with ASM module - sometimes it happens that after Login action, the site is refreshed and ASM not shown.
I found that when I'm logging in, the request is sent twice at the same time. Then it leads to error with duplicated keys found in DB. I think the main problem is the double login, but I don't know what causes it.
ANSWER
Answered 2020-Jun-12 at 12:28Turns out there was bad wro
configuration. I had the .js
files from ASM module twice on the site, once compiled in all_responsive.js
file and once again in the addons/responsive part. So everytime I did submit, both two functions sent the request.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install assisted-service
Create a quay.io or Docker Hub account if you don't already have one. These instructions refer to quay.io, Docker Hub is similar.
Create a repository called assisted-service.
Make sure you have your ~/.docker/config.json file set up to point to your account. For quay.io, you can go to quay.io -> User Settings, and click "Generate Encrypted Password" under "Docker CLI Password".
Login to quay.io using docker login quay.io.
Export the SERVICE environment variable to your Docker registry, and pass a tag of your choice, e.g., "test":
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page