thanks, that was the reason, but now it can not populate the container, although it has been created during the pod's initialization
echoing-alarm-77599
02/28/2024, 7:06 PM
just one difference with the sandbox where everything is good, after the deployment been initialized, container has been created, but it is empty, no folders: flytesnacks and metadata
echoing-alarm-77599
02/29/2024, 10:35 AM
Please disregard, issue was with internal routing. Resolved by switching to the public access.