Failure to deploy correctly.

[bstempien]

Using a trial instance of Automation Pilot stood up in early June 2024, the resulting YAML from a "Build Run Configuration" does not resulting in a running POD.

First issue is the environment variables passed in the spec are not named correctly. In release v0.0.4 the update to internal/kubernetes/metadata/metadata.go changed OPERATOR_ID, ENVIRONMENT, and INSTANCE_ID to RWP_OPERATOR_ID, RWP_ENVIRONMENT, and RWP_INSTANCE_ID but the generated YAML uses the older names without the RWP_

Second issue is the order of stanzas in the YAML seem to be off. In the spec section, adding the volume pointing to the secretName failed when the definition of the secret was in its default position at the bottom of the file. Even though the secret was created, the POD complained that it didn't exist. Moving the definition up to the second stanza (after Namespace) seemed to correct this. Other stanzas like the Service account didn't have an issue. Maybe a timing issue since the Secret is kind of large and my Kyma env is also a trial and therefore limited.

Last comment, there is mention of examples in the README.md, and I don't see any. As someone new to Automation Pilot and Kubernetes, would be nice to see examples of what can be done.

[radito3]

Hello,

This remote Automation Pilot agent is still under development and not Generally Available.
The support for it in the Automation Pilot backend services is also under development.
The k8s manifest provided by the AutoPi UI is not updated yet.
Backwards incompatible changes are expected in 0.0.x releases, as it is a Beta feature.

Could you please provide some insight into your use case?
Is this remote worker a key component of your automation flow?

[bstempien]

Currently I am just exploring this for future possibilities. I understand the Beta nature, but it will be hard to make it past Beta if every person that goes to test it out hits the roadblock of the basic implementation not even working. Most will not expend their limited time on something that doesn't even get past the basic startup. The breaking changes were made in March. It is almost July and AutoPI is not updated. I would expect SAP to be better coordinated.

…

On Thu, Jun 27, 2024 at 2:12 AM Rangel Ivanov ***@***.***> wrote: Hello, This remote Automation Pilot agent is still under development and not Generally Available. The support for it in the Automation Pilot backend services is also under development. The k8s manifest provided by the AutoPi UI is not updated yet. Backwards incompatible changes are expected in 0.0.x releases, as it is a Beta feature. Can you please provide some insight into your use case? Is this remote worker a key component of your automation flow? — Reply to this email directly, view it on GitHub <#18 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AF3TSEG362V34QEZ7TNBNELZJOUM5AVCNFSM6AAAAABJ6WNFIOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJTHA4DAMZSGM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[radito3]

To run this remote agent in a Kubernetes environment with the current version of Automation Pilot, please use the v0.0.3 release, instead of latest.

We appreciate the concerns you have about this Beta feature and are working on improving the user experience.