Installation of V1.12 with Minikube

[choonho]

Installation Guide

https://cloudforet.io/docs/setup_operation/quick_install/

If you have any issues about installation with Minikube, Please ask here!

[arup1221]

as mentioned ARM64 architecture (We do not support minikube with ARM64 CPU, such as MacBook M2)

Does in macbook m1 will it support?

[choonho]

This documentation is written at version 1.11.

Cloudforet supports ARM Docker image from version 1.12.

Please try Macbook. No one tested yet.

[arup1221]

ok, I will try.

[arup1221]

@choonho in macbook M1 it installed successfully

[achiverram28]

So Macbook M2 users cannot use?

[arup1221]

do you have docker desktop installed?

[choonho]

I also have M2 Macbook. I succeeded Cloudforet installation.
If your Helm version is 3+, it will work.

[choonho]

Helm 3.2.0+ is typo. Please update documentation. Anyone can make Pull Request.

The verified Helm version is over 3.11.0+

[achiverram28]

Yup I am making the PR

[achiverram28]

Yes I have docker desktop.
I will check once more

[achiverram28]

https://github.com/cloudforet-io/docs/pull/168

Check this PR , for the typo correct

[achiverram28]

Was able to install correctly

[Asfawh]

I am kinda confused with the first Prerequisites instruction that we need an AWS EC2 VM (Intel/AMD/ARM CPU), is there an aws account somewhere or are we using our aws account and money for the project? if not I should have a dedicated on machine for k8s cluster or minikube along with other tools?

[Asfawh]

I wish if there is a separate slack channel for discussion, and I wasn't aware if there was a zoom introduction

[Asfawh]

tried install CloudForet on my personal macbk following instruction https://cloudforet.io/docs/setup_operation/installation/on_premise/, first of all initialize-spaceone-v2iro-sz6rq: status 0/1 Completed. And checked its log see 'errmsg': 'Authentication failed' not sure what what step I missed.

https://gist.github.com/Asfawh/aaeb88385e0fadc35e0a3c75d5973a7e

[choonho]

I found one possible scenario. Did your create "initiailizer.yaml" file using following instruction?

This has some typo with wrong indentation. Please compare with
https://github.com/cloudforet-io/charts/blob/master/examples/initializer.yaml

I am highly recommend using https://github.com/cloudforet-io/charts/blob/master/examples/initializer.yaml

I also create new issue which you can create PR. Anyone is welcome.

https://github.com/cloudforet-io/docs/issues/173

[achiverram28]

I am kinda confused with the first Prerequisites instruction that we need an AWS EC2 VM (Intel/AMD/ARM CPU), is there an aws account somewhere or are we using our aws account and money for the project? if not I should have a dedicated on machine for k8s cluster or minikube along with other tools?

As of now , in the week 1 we are focussing on minikube setup and not on any cloud provider
Kindly checkout -> https://github.com/orgs/cloudforet-io/discussions/133 for the process flow

[ATREAY]

Hey everyone, does anyone know how to set up cloudforet on Windows?
I'm running into a bunch of errors, and you can check them out here.

[kumarankit999]

Hey @choonho, I have tried to setup the cloudforet on ec2 instance and almost completed but I got confused & error at 6th step where we have to create a values.yaml and edit it too!!
When I ran on ec2 it has space of 3847 Mb, this projects need is 4096 Mb, how can I achieve it!!
Can you create a Installation Video of this Project on YT So, Many folks can understand and setup it easily!!

[ATREAY]

It would be great if @choonho or anyone who has successfully set up cloudforet locally could create a video tutorial. Many mentees are having errors, and a video would be really helpful.

[ATREAY]

Hey @kumarankit999, did you manage to set up locally?

[kumarankit999]

Hey @ATREAY, I'm working and setup on ec2 instance of AWS!

[YashCommits]

i followed the cmds step by step mentioned in the docs and in the step 2 i'm getting this error, i was trying to fix it by my own but unable to so. pls help if possible

[YashCommits]

Every pod must show running status but in my case it's not. It is showing crash loop back off... So if i proceed without rectifying it will throw error in future somewhere.

BTW can you tell me that the due date of task is tomorrow after 11:59pm right ??? @Gaurav122000

Also @Gaurav122000 can you connect with me in Twitter? My username is @YashCommits in Twitter... I am asking for this so we can learn together and resolve our problems

[Gaurav122000]

@YashCommits pod takes some time to run try " kubectl get pods -n spaceone "once again 2 to 3 times if still not running then their a problem and you didn't tell on which step you are at.
I don't know the due date.
we can connect to LinkedIn - https://www.linkedin.com/in/gaurav-sharma-083786274/

[YashCommits]

Alright bro its step no. 6. And I have sent the connection on LinkedIn

[Gaurav122000]

@YashCommits delete your minikube from the docker and restart the docker then follow the step 1 to 6 again.

[Gaurav122000]

@YashCommits I accepted the invitation

[Gaurav122000]

Hey did any one found a solution for window 404 error

[kumarankit999]

Hey @choonho, where is the Maintainer/Mentor of this Mentorship Program!!?????????
Why he is not helping folks here?

[YashCommits]

How much time it took in your case to show running or completed status.... i am waiting for this for last 1 and a half hours

[choonho]

@YashCommits @Gaurav122000 @Asfawh I created 1:1 google calendar. Please reserve time-slot what you can. I will help you.

Aynone who has problem to install, please reserve google calendar.

https://calendar.google.com/calendar/u/0?cid=MTdlYzU2MjFjNDlhN2Y3ZGFlMzc1NWJhM2EwNjhkZmNhNDA2NTY0OGMxYTM4ZGZmMWE3MWViZjlmMGIwZDU1NUBncm91cC5jYWxlbmRhci5nb29nbGUuY29t

[kumarankit999]

Have you created a time slot, or we have to create it @choonho!

[choonho]

@kumarankit999 In the calendar, time-slots are already made. Update title what you want.

[choonho]

I think you can't update. Please add comment what you want at https://github.com/orgs/cloudforet-io/discussions/136

[choonho]

@YashCommits You executed initialization, before finishing the installation.

I updated docs.

[aquilinux]

Hello, i have this error trying to get TOKEN:

START SPACEONE INITIALIZE
TASK [Create Domain] ***************************************************************************************************
Start identity.Domain.create

	error_code = ERROR_GRPC_CONNECTION
	status_code = UNAVAILABLE
	message = Server is unavailable. (channel = identity:50051, message = Channel is not ready.)

(ERROR) =>

	error_code = ERROR_GRPC_CONNECTION
	status_code = UNAVAILABLE
	message = Server is unavailable. (channel = identity:50051, message = Channel is not ready.)
>> Spec: {"resource_type": "identity.Domain", "data": {"name": "root", "config": {"LANGUAGE": "ko", "TIMEZONE": "Asia/Seoul"}}, "matches": ["name"], "mode": "NO_UPDATE", "verb": {"read": "list", "create": "create", "update": "update"}, "no_verification": true}
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/site-packages/spaceone/core/pygrpc/client.py", line 447, in client
    grpc.channel_ready_future(channel).result(timeout=3)
  File "/usr/local/lib/python3.8/site-packages/grpc/_utilities.py", line 162, in result
    self._block(timeout)
  File "/usr/local/lib/python3.8/site-packages/grpc/_utilities.py", line 106, in _block
    raise grpc.FutureTimeoutError()
grpc.FutureTimeoutError

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.8/site-packages/spacectl-0.0.0-py3.8.egg/spacectl/lib/apply/task.py", line 19, in wrapper
    func(self)
  File "/usr/local/lib/python3.8/site-packages/spacectl-0.0.0-py3.8.egg/spacectl/modules/resource/__init__.py", line 76, in execute
    self._create(service, resource)
  File "/usr/local/lib/python3.8/site-packages/spacectl-0.0.0-py3.8.egg/spacectl/modules/resource/__init__.py", line 145, in _create
    create_result = _execute_api(service, resource, verb, self.spec['data'], api_version="v1", output="yaml", parser={}, silent=self.silent)
  File "/usr/local/lib/python3.8/site-packages/spacectl-0.0.0-py3.8.egg/spacectl/modules/resource/__init__.py", line 282, in _execute_api
    client = _get_client(service, api_version)
  File "/usr/local/lib/python3.8/site-packages/spacectl-0.0.0-py3.8.egg/spacectl/command/execute.py", line 271, in _get_client
    raise e
  File "/usr/local/lib/python3.8/site-packages/spacectl-0.0.0-py3.8.egg/spacectl/command/execute.py", line 265, in _get_client
    client = pygrpc.client(endpoint=f'{e.get("hostname")}:{e.get("port")}',
  File "/usr/local/lib/python3.8/site-packages/spaceone/core/pygrpc/client.py", line 449, in client
    raise ERROR_GRPC_CONNECTION(channel=endpoint, message='Channel is not ready.')
spaceone.core.error.ERROR_GRPC_CONNECTION: 
	error_code = ERROR_GRPC_CONNECTION
	status_code = UNAVAILABLE
	message = Server is unavailable. (channel = identity:50051, message = Channel is not ready.)

FINISH SPACEONE INITIALIZE

Thanks for helping

[choonho]

@aquilinux Channel is not ready means docker container is not running. Initialization must be finished after all POD is running.

[aquilinux]

thanks. fixed

[aquilinux]

Hello, today i have 404 error instead of login page but when i last checked past week all was working as expected (i worked on the site with no issues).
Kind cluster running on linux, all pods running, port forwarding in place.
What is 404 error originated from?

[choonho]

*** 5. Initialize the Configuration *** is a database operation. If you failed initialization, then execute again, it failed to initialize.
I highly recommend re-install after clean-up all. Usually 404 means frontend service is working correctly, but backend services is not working.

[Tyagiquamar]

Anyone here, I tried to install again it on manjaro but
minikube start --vm-driver=docker --memory=4096  ✔

Starting local Kubernetes cluster...
F0117 11:54:23.904072 61207 cluster.go:391] Unsupported driver: docker