Date
Flight Logs contain information relating to steps completed between 05/18 - 05/19
Key Accomplishments
- Successfully edited the configuration information within the CR. This information included fields under the sections 'shared_configuration', 'initialize_configuration', as well as the requested resources.
Challenges
- CPE initialization failed
- After applying the new CR we received errors due to something preventing the Ingress from bootstrapping acce. Whenever we would login to ACCE, we would be presented with a blank screen
Lessons Learned
- Operator deployment takes care of requesting resources for new containers. Operator deployment creates an initialization container that spins up and it does not have the ability to set up CPU and memory limits. In the future, managing resources in environment can take care of this issue.
- When applying the Ingress, give the route 53 DNS operator time to pick up the correct host name before trying to access it through the browser.
- When accessing the host, we need to create a certificate to give it a secure connection. This will prevent any "insecure connection" connection loops.
Action Items
- Followup with engineering to allow RW root fs to allow Dynatrace to work
Up Next
- Use the Operator to bootstrap the gcd domain and object store and then create a navigator desktop using the CR file.
Tracking
- Flight log was added by PR 5/30/2023