Skip to content
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

Accessing Output from Porter Installation #304

Open
hemantkathuria opened this issue Jan 31, 2024 · 1 comment
Open

Accessing Output from Porter Installation #304

hemantkathuria opened this issue Jan 31, 2024 · 1 comment
Labels
question Halp plz

Comments

@hemantkathuria
Copy link

hemantkathuria commented Jan 31, 2024

I am using version 0.8.2. I was unable to install 1.0 because of this issue. #285

I am able to fire the installation by creating an instance of Installation CRD. I am unable to find a way to access output from porter mix-ins.

I can see that there is one CRD schema called installationoutputs available here. https://github.com/getporter/operator/blob/main/config/crd/bases/getporter.org_installationoutputs.yaml but I don't see this created in my Azure AKS cluster. Do I need to perform any extra steps for the same?

Currently, we are utilizing in-cluster MongoDB, can we replace it with Azure Cosmos DB + Mongo API? Are there any performance issues?

@troy0820 @schristoff @sgettys

@hemantkathuria hemantkathuria added the question Halp plz label Jan 31, 2024
@troy0820
Copy link
Member

troy0820 commented Apr 1, 2024

Several points to address. The porter operator can provide you outputs with the installationoutputs CR however, there needs to be a GRPC server that we intend to bundle with the porter operator installation. The porter operator currently doesn't show these outputs when the outputs are updated, a gap we understand. The installationoutputs are served by the grpc endpoint and act as a state store for the output of the installation that is being done by the operator. So the performance of any different backend store from mongo/azure cosmos db should be negligible (assumption mine).

There is an effort to reduce the state store capabilities with a different approach around this and going forward with what can be more useful for the operator's existence.

Porter just released v1.0.17 and the operator will be updating it's tag and what may come is that bundled grpc server container with the porter operator to provide some installation output functionality.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Halp plz
Projects
Status: Todo
Development

No branches or pull requests

2 participants