Hi I am exploring pulumi interface for our openshift platform .. the configMap seemed to have worked well, but the pod wasn't launched and the 'pulumi up' operation crashed. It appears when the volume mounts are specified, the VolumeAttachment didn't happen which was the cause of crash. I understand there could be many sources, maybe that is why it was not generated. But any suggestions on how this is to be provided ? Patching the program doesn't seem to be a good idea .. thanks for your inputs ...
10/21/2021, 3:14 PM
can you share your code, and anything that you can help to see why this crashed?
10/23/2021, 9:29 PM
Thanks very much Jaxx Mitch helped me with that .. trying to work on a project .. will get back to you if I have issues ..
Hi Lee, Today morning Mitch gave the link to the project that you did for F5/nginx . We are in a different F5 group altogether (dataplane). I am working on a Blue-green deployment strategy where I can use pulumi which I want to showcase it. I saw your youtube video on pulumi-nginx-demo-nginx-ingress. Is that something that you could share with me ? What I want to do is create a CRD with a variable 'data_present' and 'data_contents' in a CRD. From the active fill the data_contents and and set data_present to true. Have the pulumi in the stack of one deployment, send it to the other stack and have the pod source it and become active. This would be a good presentation to our team to demo the programmatic potential of pulumi to cater to our IaC needs. Thanks
Thank you very much Lee .. I'll check it out .. One question if I may ask .. wondering if pulumi's hierchical stack allows creation of org as well .. if I were to run CICD gitlab workflow process and I want to create purpose (org), stages (project) and stacks (tasks), I would be able to do that ... this will be very useful .. thanks